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.clas
I put all of a bean's classes (impl, home and remote, as well as any
required support classes) into its jar. I believe this is required by spec.
I then create a jar containing the client bits (anything exposed as or
by an interface), then use the manifest header from client jars.
Lennart Peter