Sorry, what I meant was apps should get their classes either from their J2EE container or the relevant client JAR file!
In other words, not from j2ee.jar. Robbie -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 21 January 2004 14:43 To: Tomcat Users List Subject: RE: TC5 won't start on Xeon --SOLVED Howdy, >Apps should get any J2EE files they need from the container (eg: >servlet.jar). You're obviously entitled to your opinion, but you're wrong on this one ;) Apps aren't necessarily going to get all their J2EE files from the container. Consider the case of a servlet/JSP webapp running on tomcat wishing to communicate to a remote JMS server. The webapp must have the JMS APIs and a JMS client implementation. These are not available by default in servlet containers like tomcat, though they are in full-fledged J2EE servers. You would then obtain the jms.jar and a client implementation for your server (OpenJMS rocks!), and put them in the WEB-INF/lib directory of your webapp. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
