Ok, I have another dumb idea (at least this one I have tried and got working in my far past). Have your service implement javax.xml.rpc.server.ServiceLifecycle. You need to implement two methods, init() and destroy(), I think. Declare a new static hashtable. Add it as a new attribute on the context passed into the init(). That context is really the servlet context of the web service, but it's not obvious. (You may need to cast it as a ServletContext and store that reference as a static variable). In destroy(), obviously remove the attribute and destroy the hashtable. Now, your implementation needs to get the servlet context. I think it can be done by retrieving a property from the MessageContext. (Exact string to use escapes me). The servlet context will be around as long as the web service is up and running. You can add things into the context's own hashtable of attributes and get them from any implementation method. Did this make sense? I may have missed a minor step here and there. -jeff _____
From: Lindsey Hess [mailto:[EMAIL PROTECTED] Sent: Thursday, September 06, 2007 4:31 PM To: axis-user@ws.apache.org Subject: How do I persist parameters from one operation for use by other operations? Hi, I have an Axis web service that has five operations. The first operation that must be called contains a request object with a number of parameters (e.g., max results, timeout, etc.). The other operations need these parameters since their respective request objects only take an ID and a date. Due to design requirements, I can't persist these parameters to a database or even to an XML file on disk. So, I'm not quite sure how to persist them so that the other operations can access them. Can someone please help me? Thank you. Lindsey Hess _____ Got a little couch potato? Check out fun summer activities for kids. <http://us.rd.yahoo.com/evt=48248/*http://search.yahoo.com/search?fr=oni _on_mail&p=summer+activities+for+kids&cs=bz>
