Some more information... When my startUp method is called AxisService.getFileName() returns null.
When my init method is called ServiceContext.getAxisService().getFileName() contains the correct information. Just looks like AxisService is not fully populated with information until the session context is created. Can you explain? In my case (scope=application), it appears that I can just put all my one-time initialization in init() since I will only be creating one session. It also appears that init() is called during Axis2 deployment. I want to get all the initialization done before the first request comes in. Is this correct? However, this would not work if I needed session management. In that case I would need to put one-time initialization back in startUp. Thanks. -----Original Message----- From: Tony Dean [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 06, 2006 5:52 PM To: [email protected] Subject: [axis2]a little fustrated Hi, I have put down Axis2 1.1 and have found that some things have changed that I relied on. AxisService.getFileName use to return a URL to the service. I was able to acquire resources from my aar or exploded directory bundled with my service. This method call now returns null. Why? When you make changes moving forward, you have to ensure backward capability. Or at least document a valid reason for such change. How do I proceed now in order to get the same functionality? ServiceLifeCycle: It seems the life cycle changes you have put into 1.1 that you have to specify an additional class that contains the startUp/shutDown methods. I just want one service class that performs startUp, shutDown, init, destroy, and business logic. The startUp method creates information that must be shared with the init, and business logic methods. I'm not sure if I have the lifecycle class == service class if I get one or two instances of my class. If I get one instance then I can share information with worrying about additional calloboration. If I get two instances I will have to do what you do in your lifecycle example. That is create parameters and stuff them in axis service so that the real service code can access it. For application scope I hope that I only get one instance of my class even if the lifecycle and service class are the same. Is this the case? Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.com --------------------------------------------------------------------- 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]
