Upon further inspection, it seems that the problem comes from the SAAJ implementation. I have been able to reproduce the bug using axis saaj. The toString on the SOAPFault works, but when using a jaxp transformation, it fails as you described. Maybe you could try to raise the problem on axis lists, change your saaj implementation, or try the servicemix-http (which should not have this problem as it does not use SAAJ).
Cheers, Guillaume Nodet On 6/23/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I guess i have miunderstood the problem somewhat. The data loss appears not to be a SAAJ specific problem... Anyway, faults received by web services should be handled as JBI faults, not as normal out messages. servicemix-http handles that nicely, but I think the data loss may also appear in servicemix-http. I will try to look at it asap. Cheers, Guillaume Nodet On 6/23/06, PeteTh < [EMAIL PROTECTED]> wrote: > > > Guillaume, > > Out of interest is it a big change to get the SaajMarshaler component > working. > > To me it just seems odd that it works perfectly with the response, > unless it > contains a soap fault. > Is this something to do with the soap fault being in a different > namespace > to the normal response ? > > thanks > Pete > -- > View this message in context: http://www.nabble.com/SAAJMarshaller---soapfault-content-getting-removed-t1830872.html#a5008324 > > Sent from the ServiceMix - User forum at Nabble.com. > >
