Hi Nirmit, There was a threading problem with that model so it was removed and replaced with access to a ThreadLocal MessageContext from which you can access the OperationContext.
The code you need is: org.apache.axis2.context.MessageContext.getCurrentMessageContext().getOperationContext() David On 01/12/06, robert lazarski <[EMAIL PROTECTED]> wrote:
If your goal is to get a param from services.xml, at least one way is via AxisService. One way these days to get that on startup as you were doing before is to implement the ServiceLifeCycle interface. See the spring tutorial for an example: http://ws.apache.org/axis2/1_1/spring.html#261 HTH, Robert On 12/1/06, Nirmit Desai <[EMAIL PROTECTED]> wrote: > > Hi, > > I recently switched to the 1.1.1 latest nighty. In my service > implementation, I used to capture the operationContext by implementing the > method: > > public void setOperationContext(OperationContext oCtx) > { > } > > This was supposedly called before any of the service operation was being > called and it workd fine. However, in the latest nightly this does not > work, this method is not being called. > > My purpose is to access a service parameter from my services.xml. Can > anyone tell me how I can do this in the 1.1.1 era? > > Thanks, > > -Nirmit > > > --------------------------------------------------------------------- > 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]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
