[JBoss JIRA] Created: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
10:35 a.m.
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.CR1, JBossAS-5.1.0.Beta1
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
10:37 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://jira.jboss.org/jira/browse/JBAS-6843?page=com.atlassian.jira.plug...
]
jaikiran pai updated JBAS-6843:
-------------------------------
Description:
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.
was:
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 ?le must contain, either by inclusion or by reference, the class ?les 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 ?le contains a second ?le "by reference" if the second ?le is
named in the Class-Path attribute in the Manifest ?le of the referencing jar ?le or is
contained (either by inclusion or by reference) in another jar ?le that is named in the
Class-Path attribute in the Manifest ?le of the referencing jar ?le.
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
11:57 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://jira.jboss.org/jira/browse/JBAS-6843?page=com.atlassian.jira.plug...
]
Carlo de Wolf updated JBAS-6843:
--------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153488
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
5:51 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://jira.jboss.org/jira/browse/JBAS-6843?page=com.atlassian.jira.plug...
]
Ales Justin reassigned JBAS-6843:
---------------------------------
Assignee: Adrian Brock (was: Ales Justin)
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: Adrian Brock
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
2:46 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://jira.jboss.org/jira/browse/JBAS-6843?page=com.atlassian.jira.plug...
]
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
9:30 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://jira.jboss.org/jira/browse/JBAS-6843?page=com.atlassian.jira.plug...
]
jaikiran pai updated JBAS-6843:
-------------------------------
Attachment: SampleEAR.zip
Sample application attached. Unzip the .zip file which contains the .ear. Drop the .ear in
the deploy folder of AS.
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
Attachments: SampleEAR.zip
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
3:22 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://issues.jboss.org/browse/JBAS-6843?page=com.atlassian.jira.plugin....
]
Ales Justin updated JBAS-6843:
------------------------------
Attachment: jboss-deployers-vfs.jar
Fixed ClasspathUtils.
Metadata not created for deployments listed through Classpath
attribute of Manifest.MF files
--------------------------------------------------------------------------------------------
Key: JBAS-6843
URL: https://issues.jboss.org/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
Attachments: jboss-deployers-vfs.jar, SampleEAR.zip
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://issues.jboss.org/browse/JBAS-6843?page=com.atlassian.jira.plugin....
]
Ales Justin updated JBAS-6843:
------------------------------
Attachment: jboss-deployers-vfs.jar
2nd option/fix.
Metadata not created for deployments listed through Classpath
attribute of Manifest.MF files
--------------------------------------------------------------------------------------------
Key: JBAS-6843
URL: https://issues.jboss.org/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
Attachments: jboss-deployers-vfs.jar, jboss-deployers-vfs.jar, SampleEAR.zip
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:32 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files
[
https://issues.jboss.org/browse/JBAS-6843?page=com.atlassian.jira.plugin....
]
Ales Justin commented on JBAS-6843:
-----------------------------------
@Jaikiran: is this still an issue with AS6.0.0.Final?
Metadata not created for deployments listed through Classpath
attribute of Manifest.MF files
--------------------------------------------------------------------------------------------
Key: JBAS-6843
URL: https://issues.jboss.org/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
Attachments: jboss-deployers-vfs.jar, jboss-deployers-vfs.jar, SampleEAR.zip
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4871
days inactive
5540
days old
8 comments
4 participants
participants (4)
-
Adrian Brock (JIRA) -
Ales Justin (JIRA)
-
Carlo de Wolf (JIRA)
-
jaikiran pai (JIRA)