Hmmm, thanks for the clarification. If the session is important for downstream processing on the OUT interceptor chain, I would think you would want to put it in the SOAP header of the response. But it appears I may be wrong here--I always viewed the OUT interceptor chain being activated *after* you have constructed your SOAP response, but apparently the OUT chain is used in building the SOAP response, and hence, would need to have access to the SOAP request.
Glen 2008-04-29 Willem Jiang wrote: > Hi Glen, > > The business processing logic may not care about the the request object. > But from the transport level , you may need to use the Request object > for seeking the session or some other thing for setting up the Response > object. > > Willem > > Glen Mazza wrote: > > Because the way a web service works. You receive a request, perform > > business logic based on that request, and then send the response back to > > the client. While sending the response back to the client (i.e., while > > on the out interceptor chain), you shouldn't need to care about the > > request--if so, it probably means your business processing logic was > > incomplete. > > > > Glen > > > > 2008-04-28 gweb79 wrote: > > > >> Why do you hope not? That is an odd thing to hope for. > >> But anyway, is there a way to access the session then at this point? > >> > >> > >> Glen Mazza-2 wrote: > >> > >>> I hope not. Perhaps you should ask for another way of doing what you > >>> are trying to accomplish. > >>> > >>> > >>> > > > > > > >
