I'm deploying our EJBs in an exploded EAR. All of them need log4j.jar, as well as a couple other utility JAR files. Is there a way, through an EAR-level MANIFEST.MF file or a lib directory, to make these JARs available to all of our EJBs? I'm trying to avoic adding MANIFEST.MF Class-Path entries to each of the individual EJB JARs.
Thanks,
Eric
-
How to make a util.jar available to all classes in an EAR? (4 messages)
- Posted by: Eric F
- Posted on: June 25 2002 11:01 EDT
Threaded Messages (4)
- How to make a util.jar available to all classes in an EAR? by Marina Popova on June 26 2002 09:29 EDT
- How to make a util.jar available to all classes in an EAR? by Leonard Gurevich on June 27 2002 16:31 EDT
- How to make a util.jar available to all classes in an EAR? by Sridhar Jothilingam on July 05 2002 03:32 EDT
- How to make a util.jar available to all classes in an EAR? by Leonard Gurevich on June 27 2002 16:31 EDT
- How to make a util.jar available to all classes in an EAR? by Andrew Byala on July 11 2002 11:33 EDT
-
How to make a util.jar available to all classes in an EAR?[ Go to top ]
- Posted by: Marina Popova
- Posted on: June 26 2002 09:29 EDT
- in response to Eric F
If you don't plan on changing the jars too often - you could put them in the CLASSPATH and they would be available to all EAR files then
thanks,
Marina -
How to make a util.jar available to all classes in an EAR?[ Go to top ]
- Posted by: Leonard Gurevich
- Posted on: June 27 2002 16:31 EDT
- in response to Marina Popova
Actually it may not work because many AppServers don't use CLASSPATH, they use internal one. -
How to make a util.jar available to all classes in an EAR?[ Go to top ]
- Posted by: Sridhar Jothilingam
- Posted on: July 05 2002 03:32 EDT
- in response to Leonard Gurevich
If the util.jar consists of any User classes which will be used by the EJB's deployed, then u have to set in the MANIFEST file,
or place the util.jar in the $jboss..../lib/ext/ in this directory.
-
How to make a util.jar available to all classes in an EAR?[ Go to top ]
- Posted by: Andrew Byala
- Posted on: July 11 2002 11:33 EDT
- in response to Eric F
We ran into this exact problem ourselves with our application running on Weblogic. The way we solved it was to create a "jarLoader" EJB whose only reason for existing was to utilize its Class-Path property in the MANIFEST.MF file. We specified the jarLoader to be the first EJB that would be loaded when the app server started up, and thus all EJBs would automatically have access to its referenced jars.