>> Servlets are for developing and deploying an HTML user interface.
That's getting a little too carried away. HttpServlets are for extending a
web server, SmtpServlets are for extending a smarthost, DoomServlets....
etc.
The essence of a servlet is that it's a server-side plug in, that does
request/response (chainable) and can also do load-at-startup (good for a
socket listener service, like WebSphere admin service).
The EJS services (compiler, entity bean container, each socket listener,
etc) would all make good servlets (not to be confused with HttpServlets).
It gives server modules a nice containment.
David
"Eric R. Williams" <[EMAIL PROTECTED]> on 02/25/99 05:00:02 AM
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: David Rauschenbach/ZLAND)
Subject: Re: servlets and EJB
I agree with an earlier response to your email. Servlets and
EJB serve different roles. EJB is an architecture for developing
and deploying business services. Servlets are for developing
and deploying an HTML user interface. I've heard that Sun is
considering adding better support for EJB into the Java Server
Pages (JSP) standard (which is usually, but not required to be,
based on top of a servlet implementation).
As for servlet/EJB engines... many of the application servers
that exist today support both. BEA WebLogic and IBM WebSphere
come to mind. I also read something recently that suggested
that a future release of Oracle 8i will support servlets (it
already supports EJB).
[EMAIL PROTECTED] wrote:
>
> Hey guys,
>
> What are people's thoughts on Java servlets verses Enterprise
JavaBeans?
> It seems to me that the two concepts overlap in very interesting ways
(for
> example, both are pooled, and intended for distributed, networked
objects).
Actually, servlets are *not* distributed objects. They exist only in
the servlet engine process and they are used to service HTTP requests.
And they are not necessarily pooled (usually, they are only pooled when
the servlet implements SingleThreadModel... otherwise, a single
re-entrant
object is used).
> I
> see servlets as useful because they are request/response oriented, and
more
> lightweight to develop. Enterprise beans are general components, and
gain a
> full suite of middleware services.
Having written servlets, I find that putting your business logic inside
a servlet is---to use technical jargon---icky. You don't build good
frameworks this way.
> While these differences are important, it seems strange to me that
we have
> two seperate products in the Enterprise Java Platform that perform such
similar
> functions. Has anyone made a special lightweight enterprise bean type
that was
> a request/response oriented bean, aka a servlet? Has anyone built a
servlet
> engine on top of an EJB container?
-eric
===========================================================================
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".
===========================================================================
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".
