surely your application server will handle connection pooling for you if you set up a datasource? I use WebSphere App Server (well I work for big blue so I guess I would!) and that is how it works there. Don't know about jrun though...
regards Michael Asbridge ____________________________ Sun Certified Java 2 Programmer Application Developer (Advisory) (IBM Global Services(E-Business Application Services(Messaging Services))) location: IBM UK, North Harbour, F3T int tel: 258472 ex tel: + 44 (0)2392 568472 mobile: 07801 707 202 "The first rule of Fight Club is: no smoking." 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 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
