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

[Stuart Douglas (JIRA)]

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

Stuart Douglas commented on WFLY-3215:
--------------------------------------

This sounds like it will require weld changes, however there is no way that this will be available in time for 8.0.1, which means that it would probably end up being targeted at 9. 

I don't really think it is worth the effort, and that our solution here should just be to exclude Weld. Given that JSF 1.2 was part of EE5, and EE5 did not include CDI I don't think this is a big deal. 
                
> 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: CDI / Weld, 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