[richfaces-issues] [JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
Brian Leathem (JIRA)
jira-events at lists.jboss.org
Mon Aug 12 19:33:26 EDT 2013
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796405#comment-12796405 ]
Brian Leathem commented on RF-13017:
------------------------------------
Similarly, the JBoss JSF API should be changed to remain consistent:
_version.org.jboss.spec.javax.faces.jboss-jsf-api_2.1_spec_: 2.0.7.Final -> 2.1.19.1.Final
{code}
<dependency>
<groupId>org.jboss.spec.javax.faces</groupId>
<artifactId>jboss-jsf-api_2.1_spec</artifactId>
<version>2.1.19.1.Final</version>
</dependency>
{code}
http://search.maven.org/#artifactdetails%7Corg.jboss.spec.javax.faces%7Cjboss-jsf-api_2.1_spec%7C2.1.19.1.Final%7Cjar
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
--
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
More information about the richfaces-issues
mailing list