[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8276) Weld Extension vs. Tomcat deployer in JBoss 6

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene reopened JBAS-8276:
--------------------------------



Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.

Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.

> Weld Extension vs. Tomcat deployer in JBoss 6
> ---------------------------------------------
>
>                 Key: JBAS-8276
>                 URL: https://issues.jboss.org/browse/JBAS-8276
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Weld/CDI
>    Affects Versions: 6.0.0.M4
>            Reporter: Heiko Braun
>            Assignee: Heiko Braun
>             Fix For: No Release
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira