|
I wants to split my ejb component in two parts: One
part is what only is needed on the server (foo_ejb.jar) and one part is
what a client has to have to talk with the ejb component (foo_client.jar).
In the extreme case only FooBean.class is in the foo_ejb.jar and then Foo.class,
FooHome.class, FooPK.class (if Foo is an entity ) and any kind of data objects
that can be transferred between client and server plus any exception classes are
in the foo_client.jar. As you can see i dont want to have classes duplicated,
every class has its place to be.
Now foo_ejb.jar goes to deploy dir and i put
foo_client.jar in the client dir.
This means that foo_ejb.jar has a manifiest with a
Class-Path: ../client/foo_client.jar
Now there is another ejb component that also needs to talk to foo. In its
ejb jar file, foo2_ejb.jar is a manifest with a Class-Path:
../client/foo2_client.jar ../client/foo_client.jar.
All this works but i wonder what happens with the redeploy functionality.
Changing foo_ejb.jar or foo2_ejb.jar is ok but if i need to change
foo_client.jar, what happens then?
I guess i need to touch foo_ejb.jar to get it to catch up any changes in
foo_client.jar. Then i need to know all other components that are using
foo_client.jar and touch them also. Or how is foo_client.jar added to the
classpath?
It would be nice if the client dir had the same deployer functionality as
the deploy directory. When a client jar file was changed, the old jar was dumped
from the classloader and the updated one was loaded. And so all ejb jars also
would work with the latest one. Maybe this is not possible to do?
Any suggestion to solve this in a better way?
Lennart Petersson
www.benefit.se/english |
- Re: [JBoss-user] How to handle client jars? Lennart Petersson
