[weld-issues] [JBoss JIRA] Updated: (WELDX-126) BeanManagerProvider system does not function on Jetty
[
https://jira.jboss.org/browse/WELDX-126?page=com.atlassian.jira.plugin.sy...
]
Lincoln Baxter III updated WELDX-126:
-------------------------------------
Description:
Because Jetty forces the user to define their own JDNI binding for the Bean Manager, the
provider system currently has no way of locating this definition.
See attached JettyJndiBeanManagerProvider for solution - this provider must also be
registered in:
/META-INF/services/org.jboss.weld.extensions.beanManager.BeanManagerProvider
(https://jira.jboss.org/secure/ManageAttachments.jspa?id=12416127 )
In addition:
The documentation is out of date, since the package names of required classes were changed
during the eclipse ownership change:
(RELATED) https://jira.jboss.org/browse/WELD-584
was:
Because Jetty forces the user to define their own JDNI binding for the Bean Manager, the
provider system currently has no way of locating this definition.
http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/environments....
The documentation is out of date, since the package names of required classes were changed
during the eclipse ownership change:
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
"http://jetty.mortbay.org/configure.dtd">
<Configure id="webAppCtx"
class="org.eclipse.jetty.webapp.WebAppContext">
<New id="BeanManager"
class="org.eclipse.jetty.plus.jndi.Resource">
<Arg> <Ref id="webAppCtx"/> </Arg>
<Arg>BeanManager</Arg>
<Arg>
<New class="javax.naming.Reference">
<Arg>javax.enterprise.inject.spi.BeanManager</Arg>
<Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>
<Arg/>
</New>
</Arg>
</New>
</Configure>
This documentation is also incomplete, since a <resource-ref> must be included in
the web.xml:
<resource-ref>
<res-ref-name>BeanManager</res-ref-name>
<res-type>javax.enterprise.inject.spi.BeanManager</res-type>
<res-auth>Container</res-auth>
</resource-ref>
See attached JettyJndiBeanManagerProvider for solution - this provider must also be
registered in:
/META-INF/services/org.jboss.weld.extensions.beanManager.BeanManagerProvider
BeanManagerProvider system does not function on Jetty
-----------------------------------------------------
Key: WELDX-126
URL: https://jira.jboss.org/browse/WELDX-126
Project: Weld Extensions
Issue Type: Bug
Affects Versions: 1.0.0.Alpha2
Environment: Jetty 7.1.x
Reporter: Lincoln Baxter III
Fix For: 1.0.0.Alpha3
Attachments: jetty-env.xml, JettyJndiBeanManagerProvider.java,
org.jboss.weld.extensions.beanManager.BeanManagerProvider, web.xml
Because Jetty forces the user to define their own JDNI binding for the Bean Manager, the
provider system currently has no way of locating this definition.
See attached JettyJndiBeanManagerProvider for solution - this provider must also be
registered in:
/META-INF/services/org.jboss.weld.extensions.beanManager.BeanManagerProvider
(https://jira.jboss.org/secure/ManageAttachments.jspa?id=12416127 )
In addition:
The documentation is out of date, since the package names of required classes were
changed during the eclipse ownership change:
(RELATED) https://jira.jboss.org/browse/WELD-584
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira