Tomcat integrations with J2EE app servers

[Vasile GABURICI <ga...@ss.pub.ro>]

	Hello everybody,

	I've browsed the various J2EE documents and white papers found on
Sun's web site, but I didn't find answer to the following question:

	Does J2EE compliance from an application server imply that it will
work with any standards-compliant servlet engine?

	To particularize my question, does it mean that a J2EE certified
application server (like iPlanet 6.0) will work with Tomcat as it's
servlet/JSP engine? 

	Thanks,
	Vasile

Re: Tomcat integrations with J2EE app servers

[co...@costin.dnt.ro]

> So, what you are saying is that Tomcat is not really useful for those that    
> are in serious J2EE business, because Tomcat can only be paired with the
> EJB container from the J2EE SDK, which doesn't seem more than a proof of
> concept. Instead, someone in serious EJB business would have to throw
> $35,000 per CPU to get iPlanet 6.0 application server or another big
> hitter and use that for both business logic and presentation.

> Is this strategy deliberate, or is it just a lack of an API for EJB 
> container to servlet container communication?

Tomcat can be easily embeded in any application, all that's needed
is "glue" code. 

For J2EE all you probably need is 2 glue classes - I'll check in some code
to show how this can be done easily ( into jakarta-tomcat/src/j2ee
directory), but it's up to EJB containers to embed whatever servlet
container they choose.

The current J2EE uses a bit more because it provide implementation for
missing tomcat features - form and certificate auth, SSL. 

More details next week ( I have to finish the j2ee "glue" cleanup and
implement the features we don't have )

Costin

Re: Tomcat integrations with J2EE app servers

[Vasile GABURICI <ga...@ss.pub.ro>]

So, what you are saying is that Tomcat is not really useful for those that    
are in serious J2EE business, because Tomcat can only be paired with the
EJB container from the J2EE SDK, which doesn't seem more than a proof of
concept. Instead, someone in serious EJB business would have to throw
$35,000 per CPU to get iPlanet 6.0 application server or another big
hitter and use that for both business logic and presentation.

Is this strategy deliberate, or is it just a lack of an API for EJB 
container to servlet container communication?

	Vasile

On Sat, 10 Jun 2000, Craig R. McClanahan wrote:

> Vasile GABURICI wrote:
> 
> >         Hello everybody,
> >
> >         I've browsed the various J2EE documents and white papers found on
> > Sun's web site, but I didn't find answer to the following question:
> >
> >         Does J2EE compliance from an application server imply that it will
> > work with any standards-compliant servlet engine?
> >
> 
> >         To particularize my question, does it mean that a J2EE certified
> > application server (like iPlanet 6.0) will work with Tomcat as it's
> > servlet/JSP engine?
> >
> 
> No ... instead, what it means is that the J2EE-compliant application server
> has embedded within it a way to execute servlets and JSP pages that are
> compliant with the servlet 2.2 and JSP 1.1 specs.
> 
> You cannot just substitute a different servlet container, because the J2EE
> spec imposes additional constraints on the servlet container when run in a
> J2EE environment (for example, you have to use the same database of users and
> roles for security checks that the EJB container does).
> 
> The whole idea is that applications are portable, not containers.
> 
> >
> >         Thanks,
> >         Vasile
> >
> 
> Craig McClanahan
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
> 
> 

Re: Tomcat integrations with J2EE app servers

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Vasile GABURICI wrote:

>         Hello everybody,
>
>         I've browsed the various J2EE documents and white papers found on
> Sun's web site, but I didn't find answer to the following question:
>
>         Does J2EE compliance from an application server imply that it will
> work with any standards-compliant servlet engine?
>

>         To particularize my question, does it mean that a J2EE certified
> application server (like iPlanet 6.0) will work with Tomcat as it's
> servlet/JSP engine?
>

No ... instead, what it means is that the J2EE-compliant application server
has embedded within it a way to execute servlets and JSP pages that are
compliant with the servlet 2.2 and JSP 1.1 specs.

You cannot just substitute a different servlet container, because the J2EE
spec imposes additional constraints on the servlet container when run in a
J2EE environment (for example, you have to use the same database of users and
roles for security checks that the EJB container does).

The whole idea is that applications are portable, not containers.

>
>         Thanks,
>         Vasile
>

Craig McClanahan