ICEfaces
  1. ICEfaces
  2. ICE-6173

ace-showcase cannot be deployed on Jboss6.0.0-M5

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Beta2
    • Fix Version/s: 2.0.0
    • Labels:
      None
    • Environment:
       Jboss6.0.0-M5
    • Affects:
      Compatibility/Configuration

      Description

      ace-showcase can not be deployed on Jboss6.0.0-M5:

      13:54:48,324 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfs:///C:/Servers/jboss-6.0.0.20100911-M5/server/default/deploy/ace-showcase.war state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfs:///C:/Servers/jboss-6.0.0.20100911-M5/server/default/deploy/ace-showcase.war

      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=taglib
              at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:195) [jbossxb.jar:2.0.2.Beta7]

      Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=taglib
              at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:181) [jbossxb.jar:2.0.2.Beta7]
              at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.startElement(SaxJBossXBParser.java:370)
      [jbossxb.jar:2.0.2.Beta7]

        Issue Links

          Activity

          Hide
          Mark Collette added a comment -

          Forum posting describing how to workaround this issue:
          http://www.icefaces.org/JForum/posts/list/18055.page

          Show
          Mark Collette added a comment - Forum posting describing how to workaround this issue: http://www.icefaces.org/JForum/posts/list/18055.page
          Hide
          Mark Collette added a comment -

          First add the schema info in the ACE TLDBuilder class, and then if that's not sufficient, look into modifying the generator code to output the TLD in a manner more conforming to the schema. Sometimes this just involves outputting the tags in a different sequence.

          Show
          Mark Collette added a comment - First add the schema info in the ACE TLDBuilder class, and then if that's not sufficient, look into modifying the generator code to output the TLD in a manner more conforming to the schema. Sometimes this just involves outputting the tags in a different sequence.
          Hide
          Nicklas Karlsson added a comment -

          I think the description tag was in the wrong place (and the version number in the wrong format)

          Show
          Nicklas Karlsson added a comment - I think the description tag was in the wrong place (and the version number in the wrong format)
          Hide
          Greg Dick added a comment -

          A few things here:

          • version number in build.properties wasn't conforming to dewey-versionType format
          • Required.java has an enum for whether attributes are required, values must be yes/no or true/false. OPTIONAL and REQUIRED are invalid.
          • <documentation> elements must be earlier in both tag and attribute elements.
          • Restored the xmlns, xmlns:xsi, and xsi:schemaLocation attributes on the document node as they were mistakenly removed.
          • <display-name> element must occur earlier in the <taglib> root.

          There is still an issue with the build. At the end of the component build the tlddoc target issues the following exception:

          tlddoc:
          [mkdir] Created dir: C:\icefaces2-demo\icefaces2\ace\component\build\doc\tld
          [java] Loading and translating 1 Tag Library...
          [java] com.sun.tlddoc.GeneratorException: Error: C:\icefaces2-demo\icefaces2\ace\component\build\exploded\META-INF\components.tld does not have xmlns="http://java.sun.com/xml/ns/j2ee"
          [java] at com.sun.tlddoc.TLDDocGenerator.createTLDSummaryDoc(TLDDocGenerator.java:553)
          [java] at com.sun.tlddoc.TLDDocGenerator.generate(TLDDocGenerator.java:439)
          [java] at com.sun.tlddoc.TLDDoc.main(TLDDoc.java:217)

          I can change the xmlns attribute to: http://java.sun.com/xml/ns/j2ee, which solves the above error, but JBoss complains about expecting javaee, it is defined as the xmlns in http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd which is a mismatch.

          The above exception doesn't affect the generated output, however, and the currently checked in files creates a tld that allows applications to run in jboss 6.0.0-M5

          Show
          Greg Dick added a comment - A few things here: version number in build.properties wasn't conforming to dewey-versionType format Required.java has an enum for whether attributes are required, values must be yes/no or true/false. OPTIONAL and REQUIRED are invalid. <documentation> elements must be earlier in both tag and attribute elements. Restored the xmlns, xmlns:xsi, and xsi:schemaLocation attributes on the document node as they were mistakenly removed. <display-name> element must occur earlier in the <taglib> root. There is still an issue with the build. At the end of the component build the tlddoc target issues the following exception: tlddoc: [mkdir] Created dir: C:\icefaces2-demo\icefaces2\ace\component\build\doc\tld [java] Loading and translating 1 Tag Library... [java] com.sun.tlddoc.GeneratorException: Error: C:\icefaces2-demo\icefaces2\ace\component\build\exploded\META-INF\components.tld does not have xmlns="http://java.sun.com/xml/ns/j2ee" [java] at com.sun.tlddoc.TLDDocGenerator.createTLDSummaryDoc(TLDDocGenerator.java:553) [java] at com.sun.tlddoc.TLDDocGenerator.generate(TLDDocGenerator.java:439) [java] at com.sun.tlddoc.TLDDoc.main(TLDDoc.java:217) I can change the xmlns attribute to: http://java.sun.com/xml/ns/j2ee , which solves the above error, but JBoss complains about expecting javaee, it is defined as the xmlns in http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd which is a mismatch. The above exception doesn't affect the generated output, however, and the currently checked in files creates a tld that allows applications to run in jboss 6.0.0-M5
          Hide
          Greg Dick added a comment -

          I've checked in version 1.3 of the taglib generating tool. This solves the problem with the namespaces.

          Show
          Greg Dick added a comment - I've checked in version 1.3 of the taglib generating tool. This solves the problem with the namespaces.
          Hide
          Greg Dick added a comment - - edited

          I had this fixed, but changes for 6207 re-introduced an issue with the tld. If we're going to want to put other information into the tld for IDE's, we're going to have to do it outside the method for generating a TLD that is conformant to the schema.

          Show
          Greg Dick added a comment - - edited I had this fixed, but changes for 6207 re-introduced an issue with the tld. If we're going to want to put other information into the tld for IDE's, we're going to have to do it outside the method for generating a TLD that is conformant to the schema.
          Hide
          Greg Dick added a comment -

          I've removed the changes for 6207 from the TLDBuilder. They were in the wrong place as part of a misunderstanding.

          Show
          Greg Dick added a comment - I've removed the changes for 6207 from the TLDBuilder. They were in the wrong place as part of a misunderstanding.

            People

            • Assignee:
              Greg Dick
              Reporter:
              Mandeep Hayher
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: