Hi,
Wow, what a long message ;) I don't have time to reply to everything,
but the general answer is: tomcat is a servlet/JSP container at this
point. Not a J2EE container. Inter-operating with remote J2EE servers,
at least for us, has proven easy. We've never used tomcat 3.x, only
4.x, so I
of J2EE ownership and maintenance. Hopefully someone at Sun is listening...
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 9:28 AM
To: Tomcat Users List
Subject: RE: Classpath Issues, Tomcat 4.X and J2EE Interoperability
frustrations
,
Tomcat 4.X and J2EE Interoperability frustrations...
Yoav and JeanFrancios,
Thank you both for your replies. They were helpful and
somewhat reassuring.
At the general level:
We are aware that Tomcat is not a full J2EE container. But servlets
calling EJB's is bread
-Original Message-
From: Andrew Gilbert
Sent: Thursday, October 10, 2002 3:39 PM
To: Tomcat Users List
Cc: 'Craig R. McClanahan'; 'Jean-Francois Arcand'; 'Shapira,
Yoav'; Tim
Segall
Subject: RE: Classpath Issues, Tomcat 4.X and J2EE Interoperability
frustrations...
Craig,
I
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
We are finding this a particularly frustrating experience, and it seems to be a weak
point either/or both in specification and implementation (or a fatal flaw in our basic
approach - but would add we are consistent at least with the intent of the EJB
specs). Would appreciate input and
Andrew Gilbert wrote:
We are finding this a particularly frustrating experience, and it seems to be a
weak point either/or both in specification and implementation (or a fatal flaw in
our basic approach - but would add we are consistent at least with the intent of
the EJB specs). Would
