Hello everyone,
I have a little problem. I designed an orchestration similar to
ExposeWebService sample, but I call a web service (instead of a map) to
have a message result. The web service returns an XmlDocument. If I
assign the result to a Message, it compiles and deploys, but at
run-time the SOAP adapter returns this error:

Type System.Xml.Schema.XmlSchemaComplexContentExtension nell'assembly
System.Xml, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089 is not marked as serializable.

What is the better solution for this problem?

Thanks all,
Gionni

[ Post a follow-up to this message ]

You will likely want to examine the generated proxy code, and consider
tweaking it (or, alternatively, tweaking a private copy of the WSDL and
regenerate the proxy.)

Ideally, you could tweak the WSDL to refer to an actual schema.

Scott Colestock
www.traceofthought.net



"Gionni" <vezzosi.daniele@gmail.com> wrote in message
news:1126719086.462611.22340@f14g2000cwb.googlegroups.com...
> Hello everyone,
>   I have a little problem. I designed an orchestration similar to
> ExposeWebService sample, but I call a web service (instead of a map) to
> have a message result. The web service returns an XmlDocument. If I
> assign the result to a Message, it compiles and deploys, but at
> run-time the SOAP adapter returns this error:
>
> Type System.Xml.Schema.XmlSchemaComplexContentExtension nell'assembly
> System.Xml, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089 is not marked as serializable.
>
> What is the better solution for this problem?
>
> Thanks all,
> Gionni
>

[ Post a follow-up to this message ]

You'll  need to configure your orchestration to run in an atomic
transaction.

[ Post a follow-up to this message ]

Well, I think you want to be careful about using atomic to overcome
serialization issues.
You need to be ok with the other behavior that "atomic" implies for your
particular orchestration.

Scott Colestock



"Ben McFarlin" <mcfarlin_ben@hotmail.com> wrote in message
news:1126733660.935621.297190@g44g2000cwa.googlegroups.com...
> You'll  need to configure your orchestration to run in an atomic
> transaction.
>

[ Post a follow-up to this message ]