> 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.
>From J2EE container, they will. > 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. Precisely. Even in Tomcat's case, you shouldn't supply j2ee.jar, you should supply jms.jar ONLY. > 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. Yup! Nix. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
