aspose file tools*
The moose likes Web Services and the fly likes axis2: connection pool vs servicelifecycle Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "axis2: connection pool vs servicelifecycle" Watch "axis2: connection pool vs servicelifecycle" New topic
Author

axis2: connection pool vs servicelifecycle

Jeff Boucher
Greenhorn

Joined: Aug 18, 2008
Posts: 14
I've read a few articles and tutorials now on extending the servicelifecycle in axis2 to establish a database connection at the time a service is launched, and using that connection for the lifetime of the service. In this case, the recommendation is to create the connection in the startUp method and the cleanup in the shutDown method.

It looks like a fine approach, but I'm not clear on why this would be preferable to using a connection pool instead (ie. it seems more beneficial to be able to draw on a pool of existing connections rather than establishing a single one at startup time).

Any thoughts?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: axis2: connection pool vs servicelifecycle
 
Similar Threads
Connection Pool
Using ServiceLifecycle for WebServices
Get servlet's object from jsp
Database connection in servlet
axis2 ServiceLifeCycle is not up running