[richfaces-issues] [JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

[Brian Leathem (JIRA)]

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

Brian Leathem commented on RF-12801:
------------------------------------

You don't want to deploy your entire app to tomcat, rather you want to deploy an as-simple-as-possible (http://sscce.org/) reproducer that re-creates the problem.

As for the involved dependencies, try using the ones used by Websphere.  Have a look at the server startup log to see messages indicating what versions of the involved libraries are being started.
                
> org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-12801
>                 URL: https://issues.jboss.org/browse/RF-12801
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>    Affects Versions: 4.3.0.Final
>         Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final
>            Reporter: Erdem YILMAZ
>              Labels: ELResolver, optimization, resource, waiting_on_user, websphere
>
> when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere.
> resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour.
> we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it.

--
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