Re: null values populated from non-null response

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) as far as the interpretation of the w3c reference, i think you're quite

Re: null values populated from non-null response

2009/5/23 Timothy Waxland timothywaxl...@gmail.com: 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

Re: null values populated from non-null response

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

HTTP/XML Binding and W3CEndpointReference

I have a callback service which is registered by using a W3CEndpointreference. This works fine when used with SOPA / HTTP Binding. However, when callback endpoint uses HTTP/XML binding, seems like W3CEndpointReference is not supported on such endpoint, as I see an exception   [java]