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 Petersson wrote:
> 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.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user