[JBoss JIRA] (WFLY-2897) Including Mojarra implementation in WAR file causes `com.sun.faces.config.ConfigurationException`
4:28 p.m.
[
https://issues.jboss.org/browse/WFLY-2897?page=com.atlassian.jira.plugin....
]
Farah Juma commented on WFLY-2897:
----------------------------------
For versions of JSF other than JSF 2.2.x, accidentally including a JSF implementation in
the WAR file won't cause issues and WildFly's default JSF implementation will be
the one that's used. It seems that this error only occurs when accidentally including
JSF 2.2.x in the WAR file. WildFly's default JSF implementation will still be the one
that's used but the error seems to occur when FaceletTaglibConfigProcessor attempts to
process the facelets_jsf_core.taglib.xml file from the JSF JAR in the application's
WEB-INF/lib directory:
{code}
2014-03-17 17:05:10,140 FINE [javax.enterprise.resource.webcontainer.jsf.config] (MSC
service thread 1-8) Processing facelet-taglibrary document:
'vfs:/content/sample-1.0-SNAPSHOT.war/WEB-INF/lib/javax.faces-2.2.2.jar/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml'
2014-03-17 17:05:10,141 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC
service thread 1-8) Critical error during deployment: :
com.sun.faces.config.ConfigurationException: The tag named passThroughAttribute from
namespace http://xmlns.jcp.org/jsf/core has a null handler-class defined
{code}
The above log message does indicate that a JSF implementation has been included in the WAR
file (it references
'vfs:/content/sample-1.0-SNAPSHOT.war/WEB-INF/lib/javax.faces-2.2.2.jar/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml').
It doesn't look like there's much that can be done in terms of additional error
messages in this case since the JSF subsystem doesn't know that a WAR file includes a
JSF implementation unless the WAR_BUNDLES_JSF_IMPL context param is specified.
Including Mojarra implementation in WAR file causes
`com.sun.faces.config.ConfigurationException`
-------------------------------------------------------------------------------------------------
Key: WFLY-2897
URL: https://issues.jboss.org/browse/WFLY-2897
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JSF
Affects Versions: 8.0.0.CR1
Reporter: Lincoln Baxter III
Assignee: Farah Juma
Attachments: sample.zip
This stack trace was taken from EAP6 or JBoss AS7 - but it also occurs on Wildfly.
If possible, a nicer exception message (warning the user that they have included an
implementation of JSF when,) might be useful. But I don't know the exact dynamics
behind this interaction, so not sure what is possible here, or what "should" be
the right interaction.
I just know this was a bit hard to track down until randomly tripping on this in the POM
and removing it.
{code}
15:15:37,992 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService
Thread Pool -- 71) Critical error during deployment: :
com.sun.faces.config.ConfigurationException: The tag named passThroughAttribute from
namespace http://xmlns.jcp.org/jsf/core has a null handler-class defined
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:415)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:371)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:314)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:263)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:363)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216)
[jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at
org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at
org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156)
[jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at
org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)
[jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)
[jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[rt.jar:1.7.0_21]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_21]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4502
days inactive
4502
days old
0 comments
1 participants
participants (1)
-
Farah Juma (JIRA)