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]>
