Hi
I've got a question about weblogic 6.1.
having 2 different
EJB applications packaged in jar files, both deployed to same server, same domain.
Can the 2 applications access each other class loader (and thus classes?) without altering server classpath?
My guess is no
I'm working on a project where there are two jar's deployed.
First application with couple EJBs and util classes. Does not provide any direct services to clients.
The second applications inherits from a bunch of classes in the first application and uses the services of the 2 EJBs it declares(logging and "wannabe-dynamic querying").
But the second jar does not contain any of the classes it inherits from.
It seems to me the only way it works right now is that they(previous developers) have put both application jars in the servers own classpath(declared in the server startup startupscript). Second reason is that second Application is also using weblogics "startup class" facility to load certain resources on startup( in-house developed timer service). Since the startup class is in the applications jar file, it seems the whole jar had to be on the classpath.
I haven't worked too much on EJB components, but from my experience with webapplications this seems like a really bad idea to me. Wouldn't it be better to include everything in one application Jar file, so it could be deployed everywhere?
Am I correct or am I just crazy? While thing seems like a hack to me.
Is this a common deployment approach on real life servers?
comments?