I think the point of puttoing the outgoingchainsetupinterceptor early in the inbound chain is to create an out message and outgoing chain asap. This allows further interceptors to operate on that message/chain if they wanted to.
Whats your use case for changing it? - Dan On 3/15/07, Paibir, Ajay <[EMAIL PROTECTED]> wrote:
Hi, I noticed the OutgoingChainSetupInterceptor is part of the inbound interceptor chain operating in the PRE_LOGICAL phase. It does the following things a) Sets up the outbound message before even the message is dispatched to the implementor. b) Copy Message properties from inbound to outbound message c) Sets up the outbound interceptor chain. d) Sets up outbound fault message. I think a) and c) are done in a eager manner and should be deferred further down the inbound chain or if possible to start of outbound chain. So i am proposing to move (a),(b) to ServiceInvokeInterceptor and (c) to OutgoingChainInterceptor which intiates the outbound chain. Leave the (d) to the fault observer namely OutFaultChainInitiatorObserver. Thus eliminating OutgoingChainSetupInterceptor. Any suggestions, comments? I volunteer to do the changes if it makes sense. Regards Ajay
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
