At 05:45 PM 5/25/99 -0400, you wrote:
>David,
>
>Lee's comments are right on the mark. However, you should be aware that
>the choice of a servlet engine and application server are not necessarily
>mutually exclusive. Most application servers support EJB, load balancing,
>fail-over, database connection pooling, etc., but many do *not* support
>servlets or JSP (notable exceptions are BEA WebLogic, IBM WebSphere, and
>GemStone/J).
I am curious on which servers support database connection pooling. How does
it work? In my case I have to create a generic servlet that create a
connection pool and preload it. Other httpServlets use it by getContext().
Are you saying with some servers I can bypass creating my own connection
pool and somehow let my httpServlets to access the shared pool?
Thanks
Bing
>
>You should design your web-based applications so that servlets/JSP are
>restricted to implementing presentation logic (HTML generation) and do
>all of the "real work" in a separate set of classes that perform database
>access and implement business logic. Your business logic classes can
>either be deployed with your servlets or on an application server. In the
>latter case, servlets become "just another client" of the application
>server.
>
>Another way to look at it is to view servlet engines as lightweight,
>inexpensive application servers. You can begin your development and
>deployment on a servlet engine with a very low entry cost. You can
>introduce an application server into the architecture as you being to
>feel the need for the heavy-duty features they provide. At this point you
>can either leave the servlet engine in place, as a client to the
>application server, or you can re-deploy your servlets/JSP onto the
>application server.
>
>Vince
>
>---------------- Begin Forwarded Message ----------------
>Date: 5/25/99 3:19 PM
>Received: 5/25/99 4:05 PM
>From: Ackerman, Lee, [EMAIL PROTECTED]
>Reply-To: A mailing list for discussion about Sun Microsystem's Java
> , Se
>To: [EMAIL PROTECTED]
>
>David, I've been doing some research into this as well and some of the
>differences that I've seen so far include:
>
>- app servers provide a more sophisticated environment than a servlet
>runner. Most of the app servers are either already or are going to be
>supporting the entire JPE including EJB's , JNDI, JSP, Servlets, etc.
>- app servers provide built-in functionality such as load balancing and
>server fail-over
>-app servers include database connection pooling.
>- app servers have a higher purchase price - I believe that BEA's app
>server
>is one the less expensive servers
>
>Lee.
>
>
>> -----Original Message-----
>> From: David S. Soleno [SMTP:[EMAIL PROTECTED]]
>> Sent: Tuesday, May 25, 1999 11:48 AM
>> To: [EMAIL PROTECTED]
>> Subject: Application servers vs. servlet runners
>>
>> My company has assigned me the responsibility of evaluating and ranking
>> the currently available commercial application servers. Can anyone
>> point out for me the major differences between an application server
>> like BEA WebLogic and a servlet runner like JRun?
>>
>> --
>> David S. Soleno
>> Software Engineer
>> SciberNet, Inc.
>> Tel: (619) 824-0840
>> Fax: (619) 824-0846
>> e-mail: [EMAIL PROTECTED]
>>
>
>----------------- End Forwarded Message -----------------
>
>----------------------------------------------------------------------
>Vince Bonfanti [EMAIL PROTECTED]
>New Atlanta Communications, LLC http://www.newatlanta.com/
>----------------------------------------------------------------------
> "Java Servlet Technology Leaders"
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
