[jboss-jira] [JBoss JIRA] Assigned: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files

[Adrian Brock (JIRA)]

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

Adrian Brock reassigned JBAS-6843:
----------------------------------

    Assignee: Ales Justin  (was: Adrian Brock)


Ales, please don't assign things to me that I know little about.
This is something you worked on.

If this is not working, then this is either your annotation scanner 
(or the EJB deployer that uses it) not looking at the whole classpath
for the (sub)-deployment.

Although this usecase is generally not recommended since it can lead
to unintended consequences, e.g. things deployed twice:

JavaEE5 - 8.4.2 - 3

"
Note that the presence of component-declaring annotations in shared artifacts, 
such as libraries in the library directory and libraries referenced by more than one
module through Class-Path references, can have unintended and undesirable
consequences and is not recommended. 
"


> Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
> --------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6843
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6843
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.1.0.Beta1, JBossAS-5.1.0.CR1
>            Reporter: jaikiran pai
>            Assignee: Ales Justin
>
> If a (EJB) *deployment* jar contains a MANIFEST.MF which points to another *deployment* (not a plain jar) through the ClassPath attribute, then the deployment framework does not generate metadata for the deployment listed in MANIFEST.MF
> Ex: A.jar is an EJB3 deployment which contains a MANIFEST.MF pointing to B.jar (another EJB3 deployment). While processing A.jar (and its entries in MANIFEST.MF), the deployment framework does not generate metadata for B.jar
>  
> As per EJB3.0 core spec, section 20.3:
> The ejb-jar file must contain, either by inclusion or by reference, the class files of each enterprise bean as follows:
> - The enterprise bean class.
> - The enterprise bean business interfaces, web service endpoint interfaces, and home and component interfaces.
> - Interceptor classes.
> - The primary key class if the bean is an entity bean.
> We say that a jar file contains a second file "by reference" if the second file is named in the Class-Path attribute in the Manifest file of the referencing jar file or is contained (either by inclusion or by reference) in another jar file that is named in the Class-Path attribute in the Manifest file of the referencing jar file.

-- 
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