|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Tobias Frech
|Sent: Thursday, January 11, 2001 7:18 AM
|To: [EMAIL PROTECTED]
|Subject: [jBoss-User] Be careful with multiple jars
|
|
|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 ?
yes changing the classloader in the source tree :) will do someday
marc
|
|Ciao,
|Tobias
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|List Help?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
