[weld-issues] [JBoss JIRA] Closed: (CDITCK-78) Weld does not scan packaged jar in EAR file for Extension or the packaging is wrong

[Pete Muir (JIRA)]

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

Pete Muir closed CDITCK-78.
---------------------------

    Resolution: Done


> Weld does not scan packaged jar in EAR file for Extension or the packaging is wrong
> -----------------------------------------------------------------------------------
>
>                 Key: CDITCK-78
>                 URL: https://jira.jboss.org/jira/browse/CDITCK-78
>             Project: CDI TCK
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tests
>    Affects Versions: 1.0.0.GA
>            Reporter: Vivek Pandey
>            Assignee: Pete Muir
>             Fix For: 1.0.1.CR1, 1.1.0.CR1
>
>
> Either its a bug in Weld or its packaging issue of org.jboss.jsr299.tck.tests.extensions.container.event.ContainerEventTest.ear appears to be incorrect. 
> Here is the content of this ear file of a jsr299 tck test:
> org.jboss.jsr299.tck.tests.extensions.container.event.ContainerEventTest.ear
>   -META-INF/services/javax.enterprise.inject.spi.Extension ==> with entries for Observer classes
>   - org.jboss.jsr299.tck.tests.extensions.container.event.ContainerEventTest.jar
>   - ...
> The META-INF/services//javax.enterprise.inject.spi.Extension entries are defined as:
> org.jboss.jsr299.tck.tests.extensions.container.event.ProcessBeanObserver
> org.jboss.jsr299.tck.tests.extensions.container.event.ProcessInjectionTargetObserver
> org.jboss.jsr299.tck.tests.extensions.container.event.ProcessAnnotatedTypeObserver
> Weld does not scan org.jboss.jsr299.tck.tests.extensions.container.event.ContainerEventTest.jar for presence of Extension in the included jar file. If this behavior is not what jsr299 spec desires then a tleast the packaging should be such that the META-INF/services Extension classes are moved inside the jar file. JSR 299 is not clear on this but It seems that it should be expected to scan all the jars files included in the EAR file for presence of Extension.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira