JBoss V 3.0.3
I have an ear that contains an ejb.jar and web.war
file. In the deployment descriptor of the web.war file
(i.e. the web.xml) I have an ejb-ref to an EJB in the
ejb.jar file. The spec says that the ejb-link element
must contain the name of the jar-file followed by an
'#' followed by the ejb-name of the referenced EJB:
<ejb-ref>
<ejb-ref-name>ejb/Converter</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>de.xyz.converter.ConverterHome</home>
<remote>de.xyz.converter.Converter</remote>
<ejb-link>ejb.jar#Converter</ejb-link>
</ejb-ref>
Running the application causes an exception whereas the
SUN reference implementation is happy with this link.
If the ejb-link is changed to
<ejb-link>Converter</ejb-link>, i.e. the jar is
omitted. then the application also runs on JBoss.
The attached ear demonstrates this behaviour.
Application with ejb-link to another jar
Logged In: YES
user_id=176671
JBoss currently happily ignores the specified jar file. I
will look into this.
Logged In: YES
user_id=176671
i have commited a fix for this in CVS HEAD. could you please
re-check against CVS HEAD and tell me if it solves your
problem; if it does I will backport it into 3.0 and 3.2
respectively.
Logged In: YES
user_id=689193
Hi,
Ive the same problem, and tried 3.04 and also 3.2 RC1 and
nothing changed.
Ive read that Christian Riege commited a fix, but Im not able
to connect to CVS.
Please, coul anyone tell me when will this bug be fixed (wich
release) and how can I use Christians path do go on till
then...
Thanks a lot
David
Logged In: YES
user_id=176671
hi,
sorry for the absence but i was rather busy. as no one seems
to have complained in HEAD about the fix as of yet i will
backport this. it will take until mid next week though.
in the meantime, CVS access by sourceforge should have been
fixed by now.
Logged In: YES
user_id=176671
This is now fixed in Branch_3_2, am working on 3.0 series
ATM. might take some time, apparently 3.0 is not picking up
a nested .jar in a .war or something to the effect.
Logged In: YES
user_id=176671
fixed in 3.0 series. will be in JBoss 3.0.7 release.