"Steven Cheng[MSFT]" wrote:

> Hi TimG,
>
> From your description, you're encountering the following exception in your
> webservice(client proxy side) when applying the WSE 3.0 add-on ,correct?
>
> =============
> System.InvalidOperationException: There is an error in the XML document.
> System.NotImplementedException: The method or operation is not
> implemented.
> at
> ===============
>
> Based on my experience, such exception/error is usually caused by the
> webservice SOAP message contains some invalid character (not conform to the
> xml serialization or normalization specification) and the deserialization
> failed. For your scenario, since you said that if you using a normal
> soapHttpClientProtocol proxy, it works. But failed when using a WSE
> specific proxy, I think the problem may be specific to the certain
> character or string normalization approach of WSE(WS-* specification).
> Currently, for further troubleshooting, I would suggest you try creating a
> simplified service with a simple webmethod that return a object(simple
> class have a certain property/field of the type) that can correctly repro
> the same problem. If so, you can show me the test service and code logic so
> that I can also perform some local test against it.
>
> If you have any other finding on this, please also feel free to post here.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> ==================================================
>
>
>