OK, well, you can list something like APP-INF/lib/foo.jar in the
manifest entry if you still want the JARs in APP-INF/lib, but I'm glad
to hear you've got it working.   :)

Thanks,
    Aaron

On 8/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

"The application was successfully deployed.
The application was successfully started"

Yay!

I moved my jars from APP-INF/lib to the root and everything is happy now.
I'm new to EAR construction and somehow got the misconception that
APP-INF/lib was THE place to put library jars.

Thanks for all the help;

 --

 Jimmy Wan
 Senior Technical Lead
 21st Century Technologies, Inc.
 4515 Seton Center Parkway Suite 320
 Austin, TX 78759

 URL: http://www.21technologies.com


The information in this email and in any attachments is confidential and may
be privileged. If you are not the intended recipient, please destroy this
message, delete any copies held on your systems and notify the sender
immediately. You should not retain, copy or use this email for any purpose,
nor disclose all or any part of its content to any other person.

[EMAIL PROTECTED] wrote on 08/23/2006 11:42:27:


 > It should work if all the JARs are in an EAR and the EJB JARs have
 > MANIFEST entries referring to the other JARs.  Since you had some
 > build problems, can you crack open the EJB JAR(s) and make sure the
 > MANIFEST entries are really there, and that they refer to the correct
 > location in the EAR for the other files (paying attention to the case
 > of the entries and so on)?  I didn't think there were any problems
 > with Manifest Class-Path entries for EJB JARs in an EAR.
 >
 > Thanks,
 >      Aaron
 >
 > On 8/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
 > >
 > >
 > > The EJB jars under the root have references to the non-EJB jars
 > under APP-INF/lib in their META-INF/MANIFEST.MF files.
 > >
 > > I guess that's not correct. What's the best way to organize my EAR
file?
 > >
 > > Everything in my EAR is an EJB. No JSPs, war files or any web tier
 > constructs.
 > >
 > > Everything follows the following rough organization:
 > > Code1.jar
 > > Code2.jar
 > > EJB.jar (dependent on Code1.jar & Code2.jar)
 > >
 > > Do I need to package all the dependencies within each EJB jar?
 > >
 > >  --
 > >
 > >  Jimmy Wan
 > >  Senior Technical Lead
 > >  21st Century Technologies, Inc.
 > >  4515 Seton Center Parkway Suite 320
 > >  Austin, TX 78759
 > >
 > >  URL: http://www.21technologies.com



Reply via email to