Re: Failing to drop inbound XML element with invalid content

2014-03-17 Thread Mike Watson
Thanks Daniel. I worked that out about an hour ago and am implementing it now! Thanks for the quick reply though. It's a shame there's not an out of the box interceptor for this as it's probably a pretty common use case. Regards Mike On 18/03/2014 9:06 AM, "Daniel Kulp" wrote: > > Using a tra

Re: Failing to drop inbound XML element with invalid content

2014-03-17 Thread Daniel Kulp
Using a transform for this won’t work as the XML parser (woodstox in our case) would still not be able to parse the XML. The only way to handle this would be to write an interceptor that would run prior to the StaxInInterceptor that would take the InputSteam and wrapper it with a new InputStre

Failing to drop inbound XML element with invalid content

2014-03-17 Thread Mike Watson
Hi, I'm using CXF in a client that is consuming the MS Exchange Web Service (EWS). I'm finding that one of the elements returned by this service (UniqueHash) contains characters that are invalid in XML v1.0. As I have no control over this I'm trying to use an inbound interceptor to drop the Uniqu