This can be done with the init, however, based on trying that, the init is executed the first time a service call is made, thus adding the latency to that service call. Is this accurate?
While initializing on first service invocation may work in some cases, there should be some mechanism to do any heavy startup initialization work "out of band" so service clients don't see it at all. -Dave -----Original Message----- From: Deepal Jayasinghe (JIRA) [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 3:49 AM To: [email protected] Subject: [jira] Resolved: (AXIS2-921) Add system level initialization/cleanup hooks [ http://issues.apache.org/jira/browse/AXIS2-921?page=all ] Deepal Jayasinghe resolved AXIS2-921. ------------------------------------- Resolution: Fixed It is there in Axis2 , deploy your service in application scope. And Add init method to your service implementation class. If you want to know about this please have a look at following articles http://www.developer.com/services/article.php/3620661 http://www.developer.com/services/article.php/3613896 > Add system level initialization/cleanup hooks > --------------------------------------------- > > Key: AXIS2-921 > URL: http://issues.apache.org/jira/browse/AXIS2-921 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Reporter: Dave Cowing > > Axis2 should provide a mechanism to execute system level initialization, where resources available across services can be initialized outside of a service request. The classic use of this is to create and initialize a database pool, in order to remove the connection creation from any single service request, as well as to limit the number of database connections that can be open at a given time. > The mechanism should have access at least to the ConfigurationContext. It would be nice if it could also access a ServiceGroupContext, but I'm not sure if this will work. > As an analogy, in a servlet, this can be done using a servlet listener, which gets a message when the servlet is created and another when it's destroyed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
