myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bauke Scholtz (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Created] (MYFACES-3537) TagLibraryConfig doesn't recognize <facelet-taglib><description>
Date Thu, 03 May 2012 18:42:48 GMT
Bauke Scholtz created MYFACES-3537:
--------------------------------------

             Summary: TagLibraryConfig doesn't recognize <facelet-taglib><description>
                 Key: MYFACES-3537
                 URL: https://issues.apache.org/jira/browse/MYFACES-3537
             Project: MyFaces Core
          Issue Type: Bug
          Components: General
    Affects Versions: 2.1.7
         Environment: Windows 7 x64, JDK 1.7.0_4, Eclipse Indigo SR2, Tomcat 7.0.27, MyFaces
2.1.7
            Reporter: Bauke Scholtz


The trigger is this OmniFaces issue: http://code.google.com/p/omnifaces/issues/detail?id=9

OmniFaces has a {{<description>}} element right before {{<namespace>}} element
in the taglib.xml files which describes the taglib.
{code:xml}
<facelet-taglib id="o"
    xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd"
    version="2.0"
>
    <description>OmniFaces UI components.</description>
    <namespace>http://omnifaces.org/ui</namespace>

    ...
</facelet-taglib>
{code}


It get parsed fine on Mojarra, but on MyFaces 2.1.7 the following exception occurs:

{code}
Caused by: org.xml.sax.SAXException: Error Handling [jar:file:/C:/Users/BalusC/Documents/Work/M4N/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/wtpwebapps/omnifaces_test/WEB-INF/lib/omnifaces.jar!/META-INF/omnifaces-ui.taglib.xml@20,33]
<description>
	at org.apache.myfaces.view.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:609)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302)
	at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
	at org.apache.myfaces.view.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:788)
	... 37 more
{code}

Removing the {{<description>}} element solves the problem. But this is not what we want.
Putting the {{<description>}} element _after_ the {{<namespace>}} element also
solves the problem, but Eclipse marks the XML invalid according the XSD.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message