[jboss-jira] [JBoss JIRA] (WFLY-3215) JSF 1.2 on Wildfly 8 Final - weld-core-jsf is still referencing JSF 2.2 API

Stanley Hillner (JIRA) issues at jboss.org
Thu Apr 3 14:43:13 EDT 2014


    [ https://issues.jboss.org/browse/WFLY-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959076#comment-12959076 ] 

Stanley Hillner commented on WFLY-3215:
---------------------------------------

OK, I didn't know that the exclusions don't work for subdeployments. This way I will need to restructure my deployments. I will try this, as well as your hint regarding the slots on monday. Thank so far!

I will also try to patch the ConversationAwareViewHandler with the older implementation for our setup.
Would it be reasonable to patch the implementation so that it checks the JSF API version and tries to perform the new implementation but falls back to the legacy one in case of older JSF versions? I think this is the desired behavior since this module gets replaced by the multi-JSF installer.

Thanks a lot!
                
> JSF 1.2 on Wildfly 8 Final - weld-core-jsf is still referencing JSF 2.2 API
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-3215
>                 URL: https://issues.jboss.org/browse/WFLY-3215
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JSF
>    Affects Versions: 8.0.0.Final
>            Reporter: Stanley Hillner
>            Assignee: Farah Juma
>
> I added JSF 1.2 support by follwing [this tutorial|https://community.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersionToWildFly] and the sample project provided by Stan Silvert works fine. But when I deploy our own app I always get the following error message:
> {noformat}
> ERROR [request] UT005023: Exception handling request to /backoffice/login.faces: java.lang.NoSuchMethodError: javax.faces.context.FacesContext.getAttributes()Ljava/util/Map;
>      [exec] 	at org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHandler.java:103)
>      [exec] 	at javax.faces.application.ViewHandlerWrapper.getActionURL(ViewHandlerWrapper.java:147)
>      [exec] 	at com.sun.facelets.FaceletViewHandler.getActionURL(FaceletViewHandler.java:807)
>      [exec] 	at org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRenderer.getActionUrl(HtmlRenderer.java:77)
>      [exec] 	at org.apache.myfaces.custom.form.HtmlFormRenderer.getActionUrl(HtmlFormRenderer.java:45)
>      [exec] 	at org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlFormRendererBase.encodeBegin(HtmlFormRendererBase.java:102)
>      [exec] 	at org.apache.myfaces.custom.form.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:134)
>      [exec] 	at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:816)
>      [exec] 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:928)
>      [exec] 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
>      [exec] 	at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594)
>      [exec] 	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
>      [exec] 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
>      [exec] 	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
>      [exec] 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
> ...
> {noformat}
> This message indicates that the jsf-injection module still references a newer JSF API but not the JSF-1.2 API. I also had a look at the implementation of this module and I saw that the class ConversationAwareViewHandler which is included in the new jsf-injection module cannot work with JSF 1.2 since it calls methods from JSF 2.x.
> I also posted this issue [here|http://stackoverflow.com/questions/22758645/jsf-1-2-on-wildfly-8-final-weld-core-jsf-is-still-referencing-jsf-2-2-api] and need a solution.

--
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 jboss-jira mailing list