I have a strongly typed WebService WebMethod that returns an object that is
serializable based on an xsd schema and has promoted properties in C#.

When I add a WebReference the messageType is changed from the object and
appears to lose the ability to correlated on with an object that has not so
been changed.

Why is that?

If the ability to correlate is limited to the send and receive shapes and
they are no longer the same as when defined, how can correlation be set?  It
seems to need an extra step such as an assignment before the object can be
correlated on but by that stage the type of shape is no longer appropriate
and it seems as if the opportunity to correlate has been lost.

How can we correlate from an object that the WebReference process has
wrapped to an object that has not?

cheers
--
PeterW

[ Post a follow-up to this message ]

Hi Peter,

As far as I can think out, you can use a orchestration to subscribe and
pre-convert the different objects to the same schema's instances. This
prevent the message types being different. Then pass the instances to be
correlated.

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]