[
https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800366#comment-12800366
]
Brian Leathem commented on RF-12801:
------------------------------------
I'm sorry [~sebcramer], but as an OSS developer I don't have access to
Websphere. So unless you can reproduce it on tomcat and clearly demonstrate
that it's an issue with one of the impls of CDI or JSF, and not with
Websphere's handling of those libraries, then there isn't much I can do to
reproduce the issue.
If you are willing to work forward with us in it, that's great. Perhaps we can
take up such a discussion in the forums, and then come back to filing a
RichFaces JIRA issue if an issue is in fact found.
Honestly though, trying to re-produce this with tomcat + OpenWebbeans (Try
TomEE to make it easier) seems like a good way of eliminating the non-websphere
issues. If it fails, then we significantly narrowed down the problem.
To get started, try debugging, starting with a breakpoint here:
https://github.com/richfaces4/core/blob/master/impl/src/main/java/org/richfaces/resource/ResourceLoadingOptimization.java#L68
Step through the initialisation process, and see if you can figure out why the
ResourceLoadingOptimisation feature interferes with your container's
ELResolver. Try this, and post your results to the user form, we can carry on
the discussion there (and hopefully get more eyes/voices involved).
> 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, 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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
