Should I understand this all to say that Tomcat is not at all J2EE 1.3 compliant?
Section 6.1.2 states that a compliant web container supports EJB client API's! Section 6.4 states that a container that supports the EJB client API's must also support interoperability requirements. Section 6.11 states a container must support JAXP, including one SAX2 parser, one DOM 2 parser and one transformer. Figure 2.1 Strongly implies that our architectural assumption (web containter talking to EJB container) is a valid one. I still vote for quite confusing and somewhat misleading.... > -----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 was slowly coming to the conclusion that approaches 2 and 3 > are superior. > > Having said that, I am still somewhat bothered. It is easy to > (naively?) adopt approach 1. The two prior responses seemed > to indicate this approach was okay. Yoav is using it. And > there is currently another active thread on this list about > using Tomcat to talk with JBoss. There is certainly strong > natural motivation to want to deploy servlet container(s) > toward the edge talking to app server(s) at the core. Seems > odd to assert I should only talk to my distributed remote > object server by first putting myself inside another > distributed remote object server. > > Anyway, I appreciate your response. Thanks. > > Andy > > > > -----Original Message----- > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 10, 2002 12:56 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 11:42:05 -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... > > > > > > 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 and butter stuff. > > > > Only for an EJB server :-). > > > > Tomcat standalone has zero facilities to support this. For > > example, it > > basically ignores <ejb-ref> entries in your deployment descriptor. > > > > There are three feasible approaches: > > > > * Use a non-standard JNDI initial context, configured in a way that > > will talk to your particular EJB server. The details of this are > > very EJB-container-specific (the TOMCAT-USER archives > have comments > > from people who've been able to do it from Tomcat to the J2EE RI), > > and is not guaranteed to be available. You're also going to have > > to piece together the right classes for your particular app server > > in order to make the right stuff available. > > > > * Use a EJB+Servlet container that has Tomcat integrated in (such > > as the J2EE RI or JBoss). The container provider has solved all > > these problems for you already. > > > > * Use the servlet container provided by your EJB container vendor > > (sounds like WebLogic in your case), which also has solved all > > these problems. > > > > Anything else is way out on the fringes of technical fragility, and > > probably relies on internal APIs that are subject to change. > > That's why > > you have so many problems in each upgrade cycle -- you're > trying to do > > something very much non-mainstream. > > > > Craig McClanahan > > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
