2 Replies Latest reply on Apr 22, 2008 1:35 PM by theben

    Apparent JTidy SAX COnflict w/Seam

    theben

      Looking forward to using JSFUnit, but some jar hell is developing. We are trying JSFUnit 1.0-beta-1 with Seam 2.0.1 under JBoss 4.2.0 and JDK1.5. With all the JSFUnit jars and the jtidy jar in place Seam doesn't load and produces:

      com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! loader constraints violated when linking org/xml/sax/SAXParseException class
      at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:212)

      Removal of the jtidy jar allows an error free server load, but then the unit test produces the test report with an error:

      JTidy parser not available

      java.lang.RuntimeException: JTidy parser not available
      at com.meterware.httpunit.parsing.HTMLParserFactory.useJTidyParser(HTMLParserFactory.java:60)

      Suggestions or even ideas to debug? We tried older version of jtidy w/o luck. Thanks!

        • 1. Re: Apparent JTidy SAX COnflict w/Seam
          ssilvert

          If you use the latest JTidy snapshot then it usually works around the problem:
          http://jira.jboss.com/jira/browse/JSFUNIT-65

          Note that Seam support is not done yet and was not included with Beta 1. You can build JSFUnit yourself and use the SeamClient which extends JSFUnitClientSession. That will allow you access to conversation-scoped managed beans, though you currently will get a harmless stack track with each access.

          Sorry for the jar hell. It's also on the todo list to provide better tools that automatically turn your project into a "JSFUnified" project. If anyone in the community wants to work on that, I'd love to have some help.

          Stan

          • 2. Re: Apparent JTidy SAX COnflict w/Seam
            theben

            Indeed, using jtidy-8.0-20060801.131059-3.jar resolved the issue. Thanks!