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 method in the soap server asks for a connection from the pool and relinquishes it when finished.
Mark At 05:17 PM 09/10/2002 +0100, you wrote: >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 opinions? > >Jonathan > > >_________________________________________________________________ >MSN Photos is the easiest way to share and print your photos: >http://photos.msn.com/support/worldwide.aspx > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
