You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by michael wimmer <m....@aon.at> on 2002/08/26 23:46:14 UTC
connection pooling
hi,
I use protomatter (protomatter.sourceforge.net) for connection pooling
and for now it seems to work pretty well. However, in this group and in
the tomcat documentation, connection pooling seems always been mentioned
in relation to JNDI or tyrex.
Could anybody provide me with some information about the difference in
these approaches and their relative merits and demerits?
thanks,
Michael
Re: connection pooling
Posted by Glenn Nielsen <gl...@mail.more.net>.
Yes, any J2EE compliant app server will have the ability to create
a JNDI DataSource.
The choice of whether to use a container provided DataSource or your
own connection pool within the webapp is up to you.
I prefer a container managed JNDI DataSource.
Regards,
Glenn
Ashish Kulkarni wrote:
> Hi,
> A Question about JNDI, to use it i have to configure
> it in server.xml file, suppose if i have to change my
> app server , say to JRun, or Weblogic or
> websphere...how will it affect me,i think since all
> these are J2EE compliant servers, they must have some
> place for defining it,
> also what if i keep a xml file, with all the
> parameters for database connection in it, and keep it
> in web-inf of the application, and load it while
> starting the application from a startup servlet.
> so if i change the app server, i dont have to worry
> about setting JNDI in that app server,
> Ashish
> --- Glenn Nielsen <gl...@mail.more.net> wrote:
>
>>The advantage of letting the container (Tomcat)
>>setup a JNDI DataSource
>>is abstraction. It abstracts out the source of data
>>from the web application.
>>You no longer have to configure somewhere within
>>your web application the
>>db connection, user, password, etc.
>>
>>This allows you to have a development Tomcat
>>container configured with a
>>DataSource to a test db and your production system
>>to have a DataSource to
>>a production db. As long as each container creates
>>the same JNDI name you
>>can install the webapp and use it for development or
>>production without
>>any changes.
>>
>>Regards,
>>
>>Glenn
>>
>>michael wimmer wrote:
>>
>>>hi,
>>>
>>>I use protomatter (protomatter.sourceforge.net)
>>
>>for connection pooling
>>
>>>and for now it seems to work pretty well. However,
>>
>>in this group and in
>>
>>>the tomcat documentation, connection pooling seems
>>
>>always been mentioned
>>
>>>in relation to JNDI or tyrex.
>>>
>>>Could anybody provide me with some information
>>
>>about the difference in
>>
>>>these approaches and their relative merits and
>>
>>demerits?
>>
>>>
>>>thanks,
>>>
>>>Michael
>>>
>>
>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>><ma...@jakarta.apache.org>
>>For additional commands, e-mail:
>><ma...@jakarta.apache.org>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: connection pooling
Posted by Ashish Kulkarni <ku...@yahoo.com>.
Hi,
A Question about JNDI, to use it i have to configure
it in server.xml file, suppose if i have to change my
app server , say to JRun, or Weblogic or
websphere...how will it affect me,i think since all
these are J2EE compliant servers, they must have some
place for defining it,
also what if i keep a xml file, with all the
parameters for database connection in it, and keep it
in web-inf of the application, and load it while
starting the application from a startup servlet.
so if i change the app server, i dont have to worry
about setting JNDI in that app server,
Ashish
--- Glenn Nielsen <gl...@mail.more.net> wrote:
> The advantage of letting the container (Tomcat)
> setup a JNDI DataSource
> is abstraction. It abstracts out the source of data
> from the web application.
> You no longer have to configure somewhere within
> your web application the
> db connection, user, password, etc.
>
> This allows you to have a development Tomcat
> container configured with a
> DataSource to a test db and your production system
> to have a DataSource to
> a production db. As long as each container creates
> the same JNDI name you
> can install the webapp and use it for development or
> production without
> any changes.
>
> Regards,
>
> Glenn
>
> michael wimmer wrote:
> > hi,
> >
> > I use protomatter (protomatter.sourceforge.net)
> for connection pooling
> > and for now it seems to work pretty well. However,
> in this group and in
> > the tomcat documentation, connection pooling seems
> always been mentioned
> > in relation to JNDI or tyrex.
> >
> > Could anybody provide me with some information
> about the difference in
> > these approaches and their relative merits and
> demerits?
> >
> > thanks,
> >
> > Michael
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: connection pooling
Posted by Glenn Nielsen <gl...@mail.more.net>.
The advantage of letting the container (Tomcat) setup a JNDI DataSource
is abstraction. It abstracts out the source of data from the web application.
You no longer have to configure somewhere within your web application the
db connection, user, password, etc.
This allows you to have a development Tomcat container configured with a
DataSource to a test db and your production system to have a DataSource to
a production db. As long as each container creates the same JNDI name you
can install the webapp and use it for development or production without
any changes.
Regards,
Glenn
michael wimmer wrote:
> hi,
>
> I use protomatter (protomatter.sourceforge.net) for connection pooling
> and for now it seems to work pretty well. However, in this group and in
> the tomcat documentation, connection pooling seems always been mentioned
> in relation to JNDI or tyrex.
>
> Could anybody provide me with some information about the difference in
> these approaches and their relative merits and demerits?
>
> thanks,
>
> Michael
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>