JSP & Servlets vs. App Server

[MikeW]

I was wondering if anyone had any thoughts on using JSP & Servlets or an App
Server, like Enhydra? Does anyone see advantages or disadvantages to either
approach?

Thanks,

MikeW

[Jay]

One advantage to using an appserver, is that it will handle and db connection
pooling that you app may require. We recently went from NetDynamics to using
Servlets and JSP in a system that was database driven. We have had many hurdles
to overcome when it came to creating a resource efficient method of db connection
pooling.
The advantage to using Servlets and JSP is that you are not tied to a particular
Appserver. The portability of moving your servlets and jsps from say JRUN
to iPlanet servlet engine shouldn't require any code changes.

"MikeW" <MikeW@nospamplease.com> wrote:
>
>I was wondering if anyone had any thoughts on using JSP & Servlets or an
App
>Server, like Enhydra? Does anyone see advantages or disadvantages to either
>approach?
>
>Thanks,
>
>MikeW

[MikeW]

Jay,

Thanks for the input. I think an app server is the way I'll go. At this point
I really the Apple WebObject's capabilities. Also, the next rev, due out
late this year, will be pure Java.


MikeW

"Jay" <jaymayers@juno.com> wrote:
>
>One advantage to using an appserver, is that it will handle and db connection
>pooling that you app may require. We recently went from NetDynamics to using
>Servlets and JSP in a system that was database driven. We have had many
hurdles
>to overcome when it came to creating a resource efficient method of db connection
>pooling.
>The advantage to using Servlets and JSP is that you are not tied to a particular
>Appserver. The portability of moving your servlets and jsps from say JRUN
>to iPlanet servlet engine shouldn't require any code changes.

[jeff]

On some appservers, like silverstream, you can write your jsp and servlets
to interface with the appserver to take advantage of connection pooling,
security, and transactions.

"Jay" <jaymayers@juno.com> wrote:
>
>One advantage to using an appserver, is that it will handle and db connection
>pooling that you app may require. We recently went from NetDynamics to using
>Servlets and JSP in a system that was database driven. We have had many
hurdles
>to overcome when it came to creating a resource efficient method of db connection
>pooling.
>The advantage to using Servlets and JSP is that you are not tied to a particular
>Appserver. The portability of moving your servlets and jsps from say JRUN
>to iPlanet servlet engine shouldn't require any code changes.
>
>"MikeW" <MikeW@nospamplease.com> wrote:
>>
>>I was wondering if anyone had any thoughts on using JSP & Servlets or an
>App
>>Server, like Enhydra? Does anyone see advantages or disadvantages to either
>>approach?
>>
>>Thanks,
>>
>>MikeW
>

[Stefano]

Hi,

if you want connection pooling without an app server
go here:
http://www.codestudio.com/PoolMan/index.shtml

connection pooling is not the difference between
a simple Servlet Engine (JSP/Servlet) and AppServer.

Best Regards,
--- Stefano


"MikeW" <MikeW@nospamplease.com> wrote:
>
>I was wondering if anyone had any thoughts on using JSP & Servlets or an
App
>Server, like Enhydra? Does anyone see advantages or disadvantages to either
>approach?
>
>Thanks,
>
>MikeW

[Terry]

You might also look at http://www.javaexchange.com for connection pooling.


"Stefano" <dg70@ematic.com> wrote:
>
>Hi,
>
>if you want connection pooling without an app server
>go here:
>http://www.codestudio.com/PoolMan/index.shtml
>
>connection pooling is not the difference between
>a simple Servlet Engine (JSP/Servlet) and AppServer.
>
>Best Regards,
>--- Stefano
>
>
>"MikeW" <MikeW@nospamplease.com> wrote:
>>
>>I was wondering if anyone had any thoughts on using JSP & Servlets or an
>App
>>Server, like Enhydra? Does anyone see advantages or disadvantages to either
>>approach?
>>
>>Thanks,
>>
>>MikeW
>

[Jan]

Jeff,

Then you also have to mention that these Silverstream "pages" (as this is
how Silverstream calls its Servlets written with their interface) are very
proprietary and not portable to other application servers !!! No problem
if you plan to do all your futur projects in Silverstream. I would advice
to stick to the pure Sun Servlet API based Servlets though !!! Priorietary
solutions are always a risk, Java is a stayer !

Regards,
Jan



"jeff" <jeff@mpk.com> wrote:
>
>On some appservers, like silverstream, you can write your jsp and servlets
>to interface with the appserver to take advantage of connection pooling,
>security, and transactions.
>
>"Jay" <jaymayers@juno.com> wrote:
>>
>>One advantage to using an appserver, is that it will handle and db connection
>>pooling that you app may require. We recently went from NetDynamics to
using
>>Servlets and JSP in a system that was database driven. We have had many
>hurdles
>>to overcome when it came to creating a resource efficient method of db
connection
>>pooling.
>>The advantage to using Servlets and JSP is that you are not tied to a particular
>>Appserver. The portability of moving your servlets and jsps from say JRUN
>>to iPlanet servlet engine shouldn't require any code changes.
>>
>>"MikeW" <MikeW@nospamplease.com> wrote:
>>>
>>>I was wondering if anyone had any thoughts on using JSP & Servlets or
an
>>App
>>>Server, like Enhydra? Does anyone see advantages or disadvantages to either
>>>approach?
>>>
>>>Thanks,
>>>
>>>MikeW
>>
>