hi yep, validation fails in soapUI too (i was looking at the popup menus in the tree nodes not the editor - thanks for the tip)
an interceptor is what i was thinking too. i was really hoping to avoid it but its starting to look like i won't be able to. i'm looking into that now - fiddling with the incoming message is untidy work. thanks heaps for your input on this. Timothy. On Sun, May 24, 2009 at 12:28 AM, Andrew Clegg <[email protected]>wrote: > 2009/5/23 Timothy Waxland <[email protected]>: > > Hi > > > > thanks for responding. > > i turned on validation on the client side and it through an exception > where > > i expected it to - so i'm pretty sure their response is not correct. (i > > couldn't find the validate option in soapUI) > > It's in the right mouse button menu if you click on the actual XML > text of a request or response. But if CXF schema validation rejects > it, that's a good enough sign :-) > > There may be some JAXB option that allows you to override namespaces, > but I'm just guessing here. Failing that I guess you could write an > interceptor to 'fix' the incoming message with an XSLT transformation > (or other means) before JAXB unmarshalling takes place. Or write a > Dispatch client that processes the raw XML without using databinding > -- that way it wouldn't matter if the message didn't match the schema. > > Andrew. > > -- > :: http://biotext.org.uk/ :: >
