[
https://jira.nuxeo.com/browse/NXP-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109073#comment-109073
]
Anahide Tchertchian commented on NXP-8081:
------------------------------------------
stack trace excerpt:
{code}
Caused by: com.sun.facelets.FaceletException: Error Parsing
//default/*/jsf-facelets/galaxy/default/default/default: Error Traced[line: 4]
Attribute "a4j" bound to namespace "http://www.w3.org/2000/xmlns/"; was already
specified for element "html".
at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
at
org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:220)
{code}
> Log a better error message in case of a namespace URI conflict during teme
> parsing
> ----------------------------------------------------------------------------------
>
> Key: NXP-8081
> URL: https://jira.nuxeo.com/browse/NXP-8081
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Components: Themes
> Affects Versions: 5.5-SNAPSHOT
> Reporter: Antoine Taillefer
> Assignee: Anahide Tchertchian
> Attachments: a4j_namespace.log
>
>
> When different URIs are declared for a same namespace (for example
> {{xmlns:a4j}}) in 2 XHTML files associated with theme fragment views, the
> theme parsing crashes in {{DefaultFaceletFactory}}. See attached error log.
> This issue was detected by having 2 XHTML fragment views, one with the old
> a4j namespace URI ({{"https://ajax4jsf.dev.java.net/ajax"}}) and the other
> one with the new one ({{"http://richfaces.org/a4j"}}).
> Created issue NXP-8080 to update every XHTML file with the new a4j namespace
> URI.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
