Doh! Thanks again for the replies. I appreciate the input. The path is at least becoming clearer now...
> -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 10, 2002 4:31 PM > To: Tomcat Users List > Subject: RE: Classpath Issues, Tomcat 4.X and J2EE Interoperability > frustrations... > > > > > On Thu, 10 Oct 2002, Andrew Gilbert wrote: > > > Date: Thu, 10 Oct 2002 16:23:21 -0400 > > From: Andrew Gilbert <[EMAIL PROTECTED]> > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: Tomcat Users List <[EMAIL PROTECTED]> > > Subject: RE: Classpath Issues, > > Tomcat 4.X and J2EE Interoperability frustrations... > > > > Should I understand this all to say that Tomcat is not at > all J2EE 1.3 > > compliant? > > > > That's a fair one-liner summary. > > The more correct answer is that Tomcat complies with all of > the mandatory > Servlet 2.3 and JSP 1.2 features, plus *some* of those that are only > required by a complete J2EE platform (i.e. the JNDI naming > context, and > availability of a JDBC data source accessed via an API compatible with > J2EE standards). > > It has no support for EJB, JMS, ... so it is absolutely not a J2EE > compliant server by itself. Nobody eer claimed it was > (although I can't > help it when people make assumptions). > > What makes more confusing is that several people bundle Tomcat into a > complete J2EE-ish thing. Sun does that with the J2EE RI, for > example -- > but it's only a J2EE platform when you use all of it. But Tomcat by > itself is not a J2EE container. > > Craig > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
