.
_GMT-5___
>From: "Jonathan Roberts" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: soap and connection pooling
>Date: Thu, 10 Oct 2002 00:35:01 +0100
>MI
ED]> on 09/10/2002 17:48:59
>
>Please respond to [EMAIL PROTECTED]
>
>To:[EMAIL PROTECTED]
>cc:
>Subject:Re: soap and connection pooling
>
>
>
>We handle this very issue by creating a singleton class which handles the
>connection pool. The first time the s
g."
Mark Childerson <[EMAIL PROTECTED]> on 09/10/2002 17:48:59
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: soap and connection pooling
We handle this very issue by creating a singleton class which handles the
connection pool. The first time the
ober 09, 2002 12:17 PM
Subject: soap and connection pooling
>
> Does anyone know if connection pooling is possible via soap.
>
>
> My server side interface uses a bean which connects to a database.
>
> I'm presuming that soap runs on the server ( e.g.jrun ) and this
server
>
We handle this very issue by creating a singleton class which handles the
connection pool. The first time the soap server class (ie, the bean in your
case) is instantiated, it calls the connection pool for a connection. This
starts up the pool, which handles the connections from then on. Every
Does anyone know if connection pooling is possible via soap.
My server side interface uses a bean which connects to a database.
I'm presuming that soap runs on the server ( e.g.jrun ) and this server
handles the pool of conenctions in the same way as if my bean was running
withing jrun.
any
