>From my previous discussions (see the 'Stateful services question' thread) with the Axis2 guys I though handlers were stateful:
"There won't be two instance of same module , so you do not need to do any thing . At Axis2 start up time it create Module instance and keep that as long as server is running." So what happen? If only an instance of the handler (should) exists, why the instance fields are reset to their default value? Michele Ajith Ranabahu wrote: > Hi > >> from my previous posts I understood handlers are 'application scope', >> that is they maintain a state across different client invocations. > > Actually handlers are supposed to be stateless! They should not > maintain anything by themselves, rather they should be using the > appropriate context to store anything required. > >> I have a handler intercepting both incoming and outgoing messages and >> unfortunately I realized that instance fields are 'reset' (see logs >> below). Is there any reason for this counter intuitive behavior? >> > > So what I seem to understand is your handler implementation may not > have been done in the recommended way.Have a look at this article [1] > by Deepal which explains how the handlers work. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
