You cant have module level visibility and application level visibility at the same time.
For more info on visibility modes of Websphere , you can refer to this link http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/r nmodule.html The last mode is the default for "Single Server Advanced Edition" and the second last one is the default for "Advanced Edition". The only option you can have for saving the effort of making classpath entries in the manifests of each module is to put this jar in websphere's classpath.(which I guess should be in the "lib" folder) You can also get more info on the classloading sequence of Websphere from the docs. - Rahul -----Original Message----- From: Ashwani Kalra [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 1:16 PM To: [EMAIL PROTECTED] Subject: Re: how to access common files in jar from ejb and web modules of ear file hi, let me add more info to make my point clear I have following components at the same level directly in my ear file 1. allejbs.jar file (containing all ejbs) 2. war file (cotaining web components) 3. common.jar (required by ejb jar and war files) What currently I am doing is that I am setting the following entry in manifest file of allejbs.jar and war file Class-Path: common.jar But What I want is that I want to specify this at the ear file's manifest so that I dont have to individually give this entry. But this is not working. Harpreet this I think doent have to do anything about the scope you are talking about on WAS I will tell you later that due to this ( I am ofcourse using module level visibility). I am getting another problem. Srihari Srinivasan <[EMAIL PROTECTED] To: [EMAIL PROTECTED] ILIPS.COM> cc: (bcc: ashwani.kalra/Polaris) Sent by: A mailing Subject: Re: how to access common files in jar from ejb and web list for Enterprise modules of ear file JavaBeans development <[EMAIL PROTECTED] .COM> 03/10/2003 12:41 PM Please respond to srihari.srinivasan Hi check out the J2EE spec.............i am referring to j2ee-1_4 proposed final draft section 8.2 ************************ The following example illustrates a simple use of the bundled optional package mechanism to reference a library of utility classes that are shared between enterprise beans in two separate ejb-jar files. app1.ear: META-INF/application.xml ejb1.jar Class-Path: util.jar ejb2.jar Class-Path: util.jar util.jar ************************ looks like u need to specify them separately each time!!!! hope this helps ---------------------------------------------------------------------------- ---------------------------------------------------- S Srihari To: [EMAIL PROTECTED] cc: (bcc: Srihari Srinivasan/BTC/COMP/PHILIPS) Subject: how to access common files in jar from ejb and web modules of ear file Ashwani Kalra <[EMAIL PROTECTED] Classification: .IN> Sent by: A mailing list for Enterprise JavaBeans development <[EMAIL PROTECTED] M> 03/10/2003 12:11 PM Please respond to ashwani.kalra hi, I am having some common files in jar file(say common.jar) used by ejb and web module. If I try to set the classpath attribute in ear file manifest as 1. Class-Path: common.jar This doesnt work (doesnt pick the classes). How ever if I individually put the entry 1 in manifest files of ejb modules and webmodules, then it doesnt give the error. But I want to use the first method . Is there anything wrong. I am using WAS 4.0.1 for multiplatform. Regds Ashwani (See attached file: InterScan_Disclaimer.txt) =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
