The manifest of the referencing ejbjar must list all referenced ejbjars (ClassPath: ejbjar1.jar ejbjar2.jar ejbetc.jar). All ejbjars need to be in the ear. This is by spec. BEA has traditionally not honored this restriction. I don't know the state of WLS 8.1, but version 6 through 8.0 blindly made all jars of an ear visible to all ejb jars.
/Johan 11 jun 2005 kl. 16.26 skrev Karr, David:
I'm planning a certain organization of EJB classes and modules, and I wanted to confirm how I thought something works before I got too far down this path. I'm going to lay out some background of my question, but the final question is a small detail. I'm planning on having an app that reaches a certain "pre-build" step with a single ejb jar, containing a single EJB class and the appropriate descriptors. The application.xml will reference this module. From this, I'm planning to "clone" everything in the ejb jar, except for the class file, and produce a new ejb jar with a modified ejb-jar.xml, which references the original class name. I'll modify the application.xml to only reference the "cloned" EJB module. At deployment time, I'll include the two jar files at the root of the EAR. The "cloned" ejb-jar references the class from the original ejb-jar. They are both present at the root of the ear. Will this reference work, or do I have to do something special to get this to work? I'm building and deploying this with WebLogic 8.1SP4. ====================================================================== ===== 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".
=========================================================================== 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".
