[
https://issues.jboss.org/browse/WFLY-2897?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III commented on WFLY-2897:
------------------------------------------
As you wish... here is the stack trace from the latest Widlfly release, CR1. As you can
see, the error is the same, and it is not helpful. (In fact it is completely distracting
from the real issue.)
This is not an issue with multi-JSF support, I'm suggesting that we give the user an
error message that means something, or gives them a clue that they've included a
version of JSF in the app when they should actually deploy it as a Module. It should
certainly be possible to be more helpful when users do something wrong.
{code}
00:43:44,096 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service
thread 1-4) 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:422)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:378)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:321)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:270)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:437)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:214)
[jsf-impl-2.2.4-jbossorg-1.jar:]
at
io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
[undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:182)
[undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
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]
00:43:44,102 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed
to start service jboss.undertow.deployment.default-server.default-host./sample:
org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./sample: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
[jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
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]
Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
com.sun.faces.config.ConfigurationException: The tag named passThroughAttribute from
namespace
http://xmlns.jcp.org/jsf/core has a null handler-class defined
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:207)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
[jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
[jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
... 3 more
Caused by: java.lang.RuntimeException: 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.ConfigureListener.contextInitialized(ConfigureListener.java:273)
at
io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:182)
... 7 more
Caused by: 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:422)
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:378)
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:321)
at
com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:270)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:437)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:214)
... 9 more
{code}
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: Stan Silvert
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