[
https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217741#comment-13217741
]
Rene Gielen edited comment on WW-3767 at 2/28/12 12:38 AM:
-----------------------------------------------------------
I've updated CdiObjectFactory to
- support java:comp/env/BeanManager lookup
- support new configuration constant struts.objectFactory.cdi.jndiKey, to allow
custom setting in struts.xml
Could you please crosscheck the snapshot build? As usual, JNDI issues are hard
to write tests for ...
was (Author: rgielen):
I've updated CdiObjectFactory to
- support java:comp/env/BeanManager lookup
- support new configuration constant struts.objectFactory.cdi.jndiKey, to allow
default setting in struts.xml
Could you please crosscheck the snapshot build? As usual, JNDI issues are hard
to write tests for ...
> CDI on Tomcat + WELD. BeanManager not found on JNDI
> ---------------------------------------------------
>
> Key: WW-3767
> URL: https://issues.apache.org/jira/browse/WW-3767
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - CDI
> Affects Versions: 2.3.1.2
> Environment: Tomcat 6.0.X, 7.0.X
> Weld 1.1.5
> Reporter: Marco Malavolta
> Assignee: Rene Gielen
>
> I followed this instruction
> http://docs.jboss.org/weld/reference/1.0.0/en-US/html/environments.html in
> order to add cdi support to tomcat.
> The strut2 cdi plugin does not work because it searches the beanManager with
> those keys: "java:comp/BeanManager" and "java:app/BeanManager".
> Weld docs says "Tomcat only allows to bind entries to java:comp/env, so the
> BeanManager is available at java:comp/env/BeanManager".
> Adding the 3rd lookup in the plugin source code makes all works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
