I think the soap action should be set at SoapOutInterceptor, and retrieved at SoapInPostInterceptor. To keep our core module not polluted with Soap, it's better that we let AttachmentOutInterceptor create a cached stream to support the inner sub chain interceptors changing request headers..
> -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: 2006?12?5? 19:33 > To: [email protected] > Subject: Re: Http Request Header problem with mtom enabled > > > Hmm good point. There are one of two solutions. One, set the > SOAPAction > header earlier. Two, create a wrapped output stream (which is > easy enough): > > new OutputStream() { > public void write() { > // on the first write, serialize the prolog: > attachmentSerializer.serializeProlog(); > } > } > > Or something like that. :-) > > Where are you trying to set the SOAPAction? > > - Dan > > On 12/5/06, Li, Tao (Tom) <[EMAIL PROTECTED]> wrote: > > > > Hi Dan.D, > > > > Currently the AttachmentOutInterceptor will flush the > header part of mime > > stream to server before the binding & databinding > processing, it caused a > > problem that during binding (soap) & databinding > processing, the request > > header can't be added because the stream has already been flushed. > > So soap binding cant' add SOAPAction header when mtom is > enabled. I think > > we still needs to do caching in mtom enabled case. > > > > I will add a comment on jira 283 for this. > > > > Regards > > Tom Li > > Software Engineer > > > > IONA Asia Pacific Software Development Center > > 2/F, Unit A, Information Center > > Zhongguancun Software Park Haidian District, > > Beijing, P.R.China (100094) > > > > Tel: +86-10-82825151 - 519 > > Fax: +86-10-82825210 > > Email: [EMAIL PROTECTED] > > > > > > -- > Dan Diephouse > Envoi Solutions > http://envoisolutions.com | http://netzooid.com/blog >
