This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
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).
subject: axis2: connection pool vs servicelifecycle