SOLUTION: J2EE Packaging

Question

I've attached a JAR file that contains the code I used to learn how to
package a J2EE application into Weblogic 6.1 SP2. It makes use of the
Class-Path: keyword and shows how to lauch EJB clients via Weblogic's client
container. The code has no comments and you won't find any documentation
other than this message but it did show me how to package up my EJB
components without having to put anything in the global classpath. What
you'll find are 2 EJBs, 1 servlet and 2 EJB client programs. The goal of
the excercise was to simulate seperately developed components being packaged
together into a final J2EE application and show it could be done without
messing with the classpath settings in the startWeblogic.cmd file. The two
EJBs have identical names to verify that name collisions could be avoided.
The com.granite.core.EchoBean accepts a string and simply returns the same
string to the caller, after echoing what it heard to the screen. The
com.granite.service.EchoBean also accepts a string but forwards the string
to the core EchoBean. This was done to set up a dependency between the two
seperately packaged EJBs. Finally, a servlet, packaged up as a WAR file,
calles the service EJB, which then calls the core EJB. Again, this was done
just to set up dependencies. You'll notice that each component makes use of
log4j to log messages. This was done to set up a dependency on a 3rd party
library. I was pleased to find that each component could see all the classes
it needed and only one set of JARs existed in the application. No need to
copy jars into both the EJB jars and the WAR file. I used ANT as my build
tool and did not include weblogic.jar or log4j-1.1.3.jar. You'll need to
acquire those yourself and drop them into the lib directory. Typing ant
will build the entire EAR file and attempt to drop it into the specified
applications directory. You can invoke the servlet via the
http://localhost:7001/granite/HelloWorld URL. Finally, running ant
run-client-launcher will launch Weblogic's client container which invokes
the core EchoBean. It isn't fancy but should help answer some of the
questions I've seen posted to weblogic news groups.
Enjoy,
Ron Kurr
[j2ee-packaging-example.jar]

Answer 1

* You can place it wherever you want.
* That being said, the wherever should be specified as a value relative to the EJB-jar file.
For eg., given the following directory structure:
App-Directory/
|____________Ejb.jar
|____________Web.war
|____________/library/my-utilities.jar
The "Class-Path:" entry value should be "library/my-utilities.jar". Created Ear File but failes to validate through dcmctl validateEarFile -f myapp.ear
Thanks for your prompt reply
Ritesh