[jboss-jira] [JBoss JIRA] Updated: (AS7-202) JARs with OSGi metadata cannot be used by EE

[Jason Greene (JIRA)]

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

Jason Greene updated AS7-202:
-----------------------------

    Fix Version/s: 7.1.0.Beta1
                       (was: 7.1.0.Alpha1)


> JARs with OSGi metadata cannot be used by EE
> --------------------------------------------
>
>                 Key: AS7-202
>                 URL: https://issues.jboss.org/browse/AS7-202
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: David Lloyd
>            Priority: Critical
>             Fix For: 7.1.0.Beta1
>
>
> If a JAR such as a JDBC driver or other service provider (like MSC ServiceActivation) is deployed, and that JAR happens to have OSGi metadata on it, the deployment is invisible to, or incompatible with, most of the other deployers which actually enable these services, usually on behalf of one or more subsystems.  We need OSGi JARs to coexist on at least some level.
> A first step might be to have OSGi's modularization process use the same attachment set so that modules and resource roots can reliably be found in the DU attachments.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira