You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Marco Malavolta (Created) (JIRA)" <ji...@apache.org> on 2012/02/27 23:27:50 UTC
[jira] [Created] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
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
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
[jira] [Assigned] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "Rene Gielen (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rene Gielen reassigned WW-3767:
-------------------------------
Assignee: Rene Gielen
> 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
[jira] [Commented] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "Rene Gielen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217990#comment-13217990 ]
Rene Gielen commented on WW-3767:
---------------------------------
As soon as this stuff is crosschecked I'm going to add Wiki docs.
> 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
[jira] [Commented] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "Lukasz Lenart (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217944#comment-13217944 ]
Lukasz Lenart commented on WW-3767:
-----------------------------------
Do we have any docs about CDI plugin ?
> 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
[jira] [Issue Comment Edited] (WW-3767) CDI on Tomcat + WELD.
BeanManager not found on JNDI
Posted by "Rene Gielen (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "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
[jira] [Commented] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217783#comment-13217783 ]
Hudson commented on WW-3767:
----------------------------
Integrated in Struts2 #423 (See [https://builds.apache.org/job/Struts2/423/])
WW-3767:
- added support for servlet container JNDI lookup key java:comp/env/BeanManager
- added support for custom configuration constant to override standard lookup (Revision 1294420)
Result = SUCCESS
rgielen :
Files :
* /struts/struts2/trunk/plugins/cdi/src/main/java/org/apache/struts2/cdi/CdiObjectFactory.java
> 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
[jira] [Commented] (WW-3767) CDI on Tomcat + WELD. BeanManager not
found on JNDI
Posted by "Rene Gielen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WW-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217741#comment-13217741 ]
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: 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