struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rene Gielen (Commented) (JIRA)" <>
Subject [jira] [Commented] (WW-3767) CDI on Tomcat + WELD. BeanManager not found on JNDI
Date Tue, 28 Feb 2012 00:37:49 GMT


Rene Gielen commented on WW-3767:

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:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - CDI
>    Affects Versions:
>         Environment: Tomcat 6.0.X, 7.0.X
> Weld 1.1.5
>            Reporter: Marco Malavolta
>            Assignee: Rene Gielen
> I followed this instruction
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:!default.jspa
For more information on JIRA, see:


View raw message