Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 44698 invoked from network); 15 Mar 2007 14:50:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Mar 2007 14:50:45 -0000 Received: (qmail 95584 invoked by uid 500); 15 Mar 2007 14:50:53 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 95555 invoked by uid 500); 15 Mar 2007 14:50:53 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 95546 invoked by uid 99); 15 Mar 2007 14:50:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2007 07:50:53 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ajay.paibir@iona.com designates 62.221.12.33 as permitted sender) Received: from [62.221.12.33] (HELO emea-smg1.iona.com) (62.221.12.33) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2007 07:50:42 -0700 Received: from emea-ems1.ionaglobal.com (dutec.ie [10.2.1.125]) by emea-smg1.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id l2FFlKIh007557 for ; Thu, 15 Mar 2007 15:47:20 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C76711.410154BA" Subject: Why is OutgoingChainSetupInterceptor in inbound chain ? Date: Thu, 15 Mar 2007 14:48:44 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Why is OutgoingChainSetupInterceptor in inbound chain ? Thread-Index: AcdnEQgCsyzqTk0kRbmBrnW+6tJYnA== From: "Paibir, Ajay" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C76711.410154BA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 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. =20 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. =20 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. =20 Thus eliminating OutgoingChainSetupInterceptor. =20 Any suggestions, comments? I volunteer to do the changes if it makes sense. =20 Regards Ajay =20 ------_=_NextPart_001_01C76711.410154BA--