You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Geronimo 3 and NoClassDefFoundError org/w3c/dom/ElementTraversal
Using/setting Lift Props in resources/properties/default.props causes a NoClassDefFoundError org/w3c/dom/ElementTraversal on application start when used in the Geronimo 3 application server.
The problem seems to be related to specific xml-apis.jar versions some posts indicates that xml-apis-1.4.01 should work as it includes ElementTraversal (other/older versions do not).
Google search:
java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal
java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal petersson.peter
Reminder:
Check dependency tree for transient pulld in xml-apis versions to see if there may be a version clash problem. Check geronimo 3 xml-apis version (is it endorsed?)
The text was updated successfully, but these errors were encountered:
karma4u101
changed the title
Geronimo 3 and NoClassDefFoundError org/w3c/dom/ElementTraversal
Using/setting Lift Props in resources/properties/default.props causes a NoClassDefFoundError
Jul 11, 2016
Geronimo 3 and NoClassDefFoundError org/w3c/dom/ElementTraversal
Using/setting Lift Props in resources/properties/default.props causes a NoClassDefFoundError org/w3c/dom/ElementTraversal on application start when used in the Geronimo 3 application server.
The problem seems to be related to specific xml-apis.jar versions some posts indicates that xml-apis-1.4.01 should work as it includes ElementTraversal (other/older versions do not).
Google search:
java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal
java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal petersson.peter
Reminder:
Check dependency tree for transient pulld in xml-apis versions to see if there may be a version clash problem. Check geronimo 3 xml-apis version (is it endorsed?)
The text was updated successfully, but these errors were encountered: