Actually a Servlet does live in a container which differs in the wire
protocol being used (HTTP vs RMI/IIOP) and the semantics (service vs.
bean methods, different sessions, no entities). But other than that, the
same transaction management, JNDI naming context and JDBC/JMS connection
pooling apply to both.
Persistence is not currently defined for Servlets, though EJB is not the
only persistence solution. The Servlet 2.2 API adds the notion of
serializable sessions that can be potentially persisted.
We are beta testing a version of Tomcat-Tyrex which adds the
transactions, naming context and JDBC connection pooling to a Servlet
engine, and a future version will also include persistence for Servlet
sessions. This is all open source, you can check it out at
tyrex.exolab.org.
arkin
"J�r�me Beau" wrote:
>
> A servlet is not an EJB Component, as it does not live in the EJB
> framework which provide various features such as transaction
> management, persistence and so on. A servlet is much more a server
> gateway (most of the time HTTP/Web gateway) which can be a client for
> EJB components.
>
> David Grospellier CROSS SYSTEM wrote:
>
> > Hi, I'm a real beginner in EJB technologies, and I want to know
> > if a servlet is like a EJB component ? What is the difference if
> > there's one ? Thank you David GROSPELIERCROSS SYSTEMS
> > [EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
