This content has been marked as final.
Show 2 replies
-
1. Re: Bug in EAR deployment
jaikiran Feb 25, 2011 2:55 AM (in response to thomas10)thomas10 wrote:
Hello,
I am using jboss 6.0.0 final and have a problem/bug/misunderstanding:
. Bean1 has a Class-Path reference to Bean2 in its manifest.
The Java EE spec says this:
JavaEE 6 EE.8.5.2 Bullet 4: 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.
So don't use the Class-Path attribute in MANIFEST.MF to point to a jar containing the bean implementations. Remove that Class-Path entry and you should get past the issue.
-
2. Re: Bug in EAR deployment
thomas10 Feb 25, 2011 3:51 AM (in response to jaikiran)Thanks for your clarification.
So is there a mechanism to share artifacts (with annoted ejbs in it) that I am not aware of? Of course I could declare interfaces for these offending beans but this restricts the no-interface ejbs to internal use only, right?