Weld Extension vs. Tomcat deployer in JBoss 6
---------------------------------------------
Key: WELD-578
URL:
https://jira.jboss.org/browse/WELD-578
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Reporter: Heiko Braun
When I deploy a web application that contains CDI beans to JBoss6-M4 I can see that bean
deployment being executed two times. First the CDI deployer kicks in, then Tomcat
deployer re-deploys the war archive, which causes a second execution of the extension:
12:20:34,082 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4)
12:20:34,516 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai
Service: class com.foo.server.HelloWorldService
12:20:34,564 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component
as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService
12:20:34,583 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy,
ctxPath=/funky-app
12:20:34,720 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at
java:comp/BeanManager
12:20:39,776 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] undeploy,
ctxPath=/funky-app
12:20:40,246 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4)
12:20:40,733 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai
Service: class com.foo.server.HelloWorldService
12:20:40,844 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component
as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService
12:20:40,856 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy,
ctxPath=/funky-app
12:20:40,929 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at
java:comp/BeanManager
Shouldn't it be the execution the extension tight to the tomcat deployer lifecycle?
I.e. be dependent on it's meta data?
--
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