3 Replies Latest reply on Nov 26, 2006 9:35 AM by sidewinder

    JSTL xml tags, JAXEN conflict?

    tmccobb

      I have a JSTL 1.0/JSF app deployed to 3.2.7, and everything works fine EXCEPT the JSTL X (xml) tags. As soon as I try a x:forEach, I get java.lang.NoSuchMethodError: org.jaxen.dom.DocumentNavigator.getInstance().....
      jaxen-full.jar is in the /WEB-INF/lib as well as in the jbossweb-tomcat50.sar, and Java2ClassLoadingCompliance is set to false. I have run out of ideas.

      T. McCobb

        • 1. Re: JSTL xml tags, JAXEN conflict?
          sidewinder

          I have the same problem. A war calling "DocumentNavigator.getInstance()" in the Servlet-load-method causes the following exception:

          2006-11-25 00:41:04,500 FATAL [moa.id.auth] Fehler beim Starten des Service MOA ID Authentisierung
          Root exception:
          java.lang.NoSuchMethodError: org.jaxen.dom.DocumentNavigator.getInstance()Lorg/jaxen/dom/DocumentNavigator;
           at at.gv.egovernment.moa.util.XPathUtils.<clinit>(XPathUtils.java:34)
          ...
          

          JBoss: 3.2.6

          best regards,
          dominik

          • 2. Re: JSTL xml tags, JAXEN conflict?
            sidewinder

            a few more data:

            WinXP SP2 full patched
            JDK 1.5.0 Update 7 with JCE Unlimited Strength Jurisdiction Policy Files 5.0

            • 3. Re: JSTL xml tags, JAXEN conflict?
              sidewinder

              seems to be some kind of class loading problem maybe. but i didn't manage to understand how to use the wiki-stuff about class loading to solve my problem :(