[jira] [Resolved] (WW-3767) CDI on Tomcat + WELD. BeanManager not found on JNDI

["Rene Gielen (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rene Gielen resolved WW-3767.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.2

JNDI lookup was fixed. Documentation is assigned to task WW-3785
                
> 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
>             Fix For: 2.3.2
>
>
> 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