Dear all,
I found the email below in the archives about some of the challenges of using
multiple jar files and I am having problems in this area.
I am trying to do this
EJB JAR 'A' EJB JAR 'B'
bean 'a' -- calls -> bean 'b'
I arrange for the EJB JAR B to be deployed first but when I try to deploy EJB
JAR A I get an error saying bean 'b' is not found within this application.
I don't want to combine my beans into on jar file (and I would argue I
shouldn't need to). I have tried putting the Home,Remote and implementation
classes of the bean 'b' into a seperate jar file in the CLASSPATH as well as
in the ext directory.
Any assistance would be greatly appreciated.
TIA
Tom Daly
>From the Archives ...
Hi guys!
There were some threads about how you do things with multiple jars. So
here are my $.02 :
a) Be aware that beans in one jar can't access/see classes in other
jars. It is intended to be that way.
b) To solve a) some people suggest adding the jars to /lib/ext/ or
extending the classpath to include the jars in the deployment directory.
Be aware that there could be a big problem with that. Since the jar is
in the classpath now and the container starts looking for ejb-jar.xml it
may get it from the jar in the classpath and not from the jar it
actually wants to deploy !
c) There are two solutions I am aware of: 1) include everything in one
jar and merge the descriptors or 2) only include the remote and home
interfaces into one jar you can include into the class-path (NO
ejb-jar.xml). Be careful with updates of your interfaces then.
Any other solutions ?
Ciao,
Tobias
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
