I'm deploying an J2EE application as an ear file with one war and multiple EJB jars. If some of the EJBs in a.jar will act as clients to EJBs in b.jar, is there a preferred way to deploy it? Several options I've considered:
1. Duplicate the home and remote interfaces and any other classes I need from b.jar into a.jar.
2. Create a b-client.jar with the necessary classes and refer to it in the Classpath element of a.jar's manifest.
3. Just put b.jar in a.jar's manifest. (I'm not sure this will work.)
In any one of these approaches "the" right way? Or is there a better way I haven't considered?
Roger Chung-Wee
Ranch Hand
Joined: Sep 29, 2002
Posts: 1683
posted
0
You have a single application which will be loaded by a classloader. This is why you should always package your app as an EAR. Just deploy it and your code should work.
Also remember that if you have one jar file in your ear need a class in one of the other jar files, I believe you need to put that other jar file info into the manifest for the first jar file.
0
