[
https://jira.jboss.org/browse/JBAS-8660?page=com.atlassian.jira.plugin.sy...
]
Adam Warski commented on JBAS-8660:
-----------------------------------
Heh - that simple? But it worked :). I don't have any beans (java classes) in the war
hence I didn't put beans.xml in there. Now that I think of it in a way it's
logical that beans.xml need to be there, but certainly not obvious. Anyway, the error
message needs improvements ;).
But there's a much bigger problem - the beans defined in the jar are not visible in
the war - something that used to work (for certain in M2 and M4). On the screen you should
see "Hello World", but there's nothing (#{test == null} is true where test
is an @Named bean in the jar).
And there's the same exception, about not being able to find the BeanManager during
undeploy.
Cannot deploy a Weld application which uses Weld Extensions
-----------------------------------------------------------
Key: JBAS-8660
URL:
https://jira.jboss.org/browse/JBAS-8660
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.CR1
Reporter: Adam Warski
Attachments: demo-app.tar.gz
Weld extensions version: 1.0.0.Beta1
Weld version: 1.1.0.Beta2 (as in AS 6 CR1)
Stack trace:
http://pastie.org/1320406
17:16:05,525 INFO [config] Unsanitized stacktrace from failed start...:
java.lang.IllegalStateException: Could not locate a BeanManager from the providers
org.jboss.seam.faces.beanManager.FacesServletContextBeanManagerProvider(20),
org.jboss.weld.extensions.beanManager.DefaultJndiBeanManagerProvider(11),
org.jboss.weld.extensions.beanManager.DefaultJndiBeanManagerProvider(11),
org.jboss.weld.extensions.beanManager.JBossJndiBeanManagerProvider(10),
org.jboss.weld.extensions.beanManager.ServletContainerJndiBeanManagerProvider(10),
org.jboss.weld.extensions.beanManager.JBossJndiBeanManagerProvider(10)
(...)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira