What part of the ServiceClass is supposed to be called on startup in application scope? I am using axis2 1.4.1, and the constructor of the ServiceClass is only called when the first method is invoked.
I also implemented the init() and destroy() methods. The init() method is also called when the first method is invoked. The order of things, seems to be: 1. Service is deployed 2. ServiceLifeCycle.startup() is called 3. Everything just sits there 4. method is called (in-only MEP) 5. ServiceClass constructor called 6. ServiceClass init() method is called. The ServiceClass does last the lifetime of the Server. That said, is there a workaround by which I can instantiate ServiceClass on startup? I am thinking I can invoke something in ServiceLifeCycle.startup(), or write a script that invokes a soap client on startup. We are evaluating if we should use axis2 for one of our projects at our company, and this is a must-have requirement. Cheers rouble On Sun, Jan 18, 2009 at 11:58 AM, Deepal Jayasinghe <[email protected]>wrote: > Well ServiceLifeCycle class is different thing, anyway you may use that > to do the initialization logic. > As I remember correct when you deploy a service in application scope it > should initialize the class system startup time, if that does not work > then it is a bug. > > Deepal > > rouble wrote: > > Hi All, > > > > I have an "application" scope axis2 web service. I want the > > ServiceClass to be instantiated on startup, as opposed to when the > > first method is invoked. > > > > I found (and implemented) a ServiceLifeCycle class, but I don't know > > how exactly to instantiate the ServiceClass from within the startup() > > method. > > > > Any help will be appreciated. > > > > TIA, > > rouble > > -- > Thank you! > > > http://blogs.deepal.org > http://deepal.org > > -- this message is composed of 100% recycled ascii
