Hi,

I've found a workaround to solve this issue. Adding writer.flush(); in
ElementImpl.internalSerialize solves the problem. Although this issue is
linked with release 1.2.5 of axiom-dom, I'm curious if anybody else had the
same issue.

Regards, Stefan.


stlecho wrote:
> 
> Hi,
> 
> I'm using Axis2 v1.3 and I've remarked that sometimes the SOAP Body is
> modified after the call to element.serializeAndConsume(bytesOut, format).
> This call is performed in SOAPMessageFormatter.getBytes(MessageContext
> msgCtxt, OMOutputFormat format).
> 
> The SOAP Body that is being changed originally contains
> <client><nationalNumber>...</nationalNumber><enterpriseNumber>...</enterpriseNumber><eid
> />    <callerId>...</callerId><language>fr</language></client>. After the
> element.serializeAndConsume(bytesOut, format) call this Body is
> transformed to <client>...</ent> or <client>...</lient>. The client end
> tag is in this case not correct.
> 
> The annoying thing is that this transformation happens from time to time
> and is completely random, except that it's always the client element that
> is affected.
> 
> Any help with this issue would be highly appreciated :o).
> 
> Regards, Stefan.
> 

-- 
View this message in context: 
http://www.nabble.com/-Axis2-1.3--Content-of-SOAP-Body-gets-changed-after-serializeAndConsume-tp16585918p16607899.html
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to