Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 33001 invoked from network); 26 Oct 2006 13:02:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 13:02:57 -0000 Received: (qmail 26379 invoked by uid 500); 26 Oct 2006 13:03:07 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 26320 invoked by uid 500); 26 Oct 2006 13:03:07 -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 26308 invoked by uid 99); 26 Oct 2006 13:03:07 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2006 06:03:07 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [216.73.126.120] (HELO mail.envoisolutions.com) (216.73.126.120) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2006 06:02:50 -0700 Received: from [192.168.3.103] (c-71-205-191-164.hsd1.mi.comcast.net [71.205.191.164]) by mail.envoisolutions.com (Postfix) with ESMTP id CCF721009D; Thu, 26 Oct 2006 05:54:57 -0700 (PDT) Message-ID: <4540B1E6.2020502@envoisolutions.com> Date: Thu, 26 Oct 2006 09:02:30 -0400 From: Dan Diephouse User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: cxf-dev@incubator.apache.org Cc: "Liu, Jervis" Subject: Re: Problem with interceptor chain References: <9A4696F35B459043970EE4A85A3173900667BF@amer-ems1.IONAGLOBAL.COM> <200610241138.50079.daniel.kulp@iona.com> In-Reply-To: <200610241138.50079.daniel.kulp@iona.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Daniel Kulp wrote: >Jervis, > > > >>I've come across an issue when trying to make SOAPHandlerInterceptor >>able to read SOAPMessage in the outbound direction. Basically the >>problem is that our current outbound interceptor chain is not a flat >>chain, it looks like below: >> >>WrapperClassOutInterceptor >>LogicalHandlerInterceptor >>MessageSenderInterceptor >> StaxOutInterceptor >> SOAPHandlerInterceptor >> SoapOutInterceptor >> WrappedOutInterceptor >> BareOutInterceptor >> >> > > >Out of curiosity, why couldn't the SOAPHandlerInterceptor do the same >thing. Make it: > > WrapperClassOutInterceptor > LogicalHandlerInterceptor > MessageSenderInterceptor > StaxOutInterceptor > SOAPHandlerInterceptor > SoapOutInterceptor > WrappedOutInterceptor > BareOutInterceptor > >Basically, the SOAPHandlerInterceptor would create a StAX writer that >writes to the SAAJ model/DOM and then calls: >message.getInterceptorChain().doIntercept(message); > >When that returns, the SAAJ model should be fully built up at which point >you can call the SAAJ handlers. When they are done, stream the SAAJ to >the output stream. > > > > Because what happens if there is an interceptor after the SOAPHandlerInterceptor which wants to use the SAAJ/DOM tree? Like WS-Security? - Dan -- Dan Diephouse (616) 971-2053 Envoi Solutions LLC http://netzooid.com