Originally posted by Peter Johnson:
If you place the JAR file in the base directory of the EAR, and include it in the application.xml file, then it will be available to both EJBs and WAR.
In 5.0, you could also place it in the lib directory within the EAR. Then you do not need to add it to the application.xml file. I am not sure if this scheme would work on 4.2.x.
Peter, It worked! but, just curious to know: If we add the jar file to the class path thru manifest files(Class-Path: common.jar) in ejb-jar and war files. is common.jar accessible to both the modules?