XML Serializing unknown objects

[Chris Smith]

I bet this question has been asked quite a bit, but if someone can point me
in the right direction, I would be very grateful.

I would like to write a assembly (dll) that one of the functions will act as
a task router. This router will take different objects of many types, and
pass that object to the correct webservice for handling. Seems that doing
this creates quite a bit of serialization issues, especially when the
webservice returns a modified object to the task router for forwarding to
the client.

Example:

Client App -> Task Router -> Web Service (Altered object)
Web Service -> Task Router -> Client App

How can I make the task router not care about class types. I really don't
want to code every possible class type into the router as new apps will also
use this. Is there a method for doing what I am trying, seems there should
be a way to avoid the constant updating and maintenance.

Thanks,

Chris

[AA]

My opinion..

Use reflection for dynamic load of classes and serialization/deserialization
AA
"Chris Smith" <us**@email.com> wrote in message
news:e9*************@TK2MSFTNGP11.phx.gbl...

I bet this question has been asked quite a bit, but if someone can point me in the right direction, I would be very grateful.

I would like to write a assembly (dll) that one of the functions will act as a task router. This router will take different objects of many types, and
pass that object to the correct webservice for handling. Seems that doing
this creates quite a bit of serialization issues, especially when the
webservice returns a modified object to the task router for forwarding to
the client.

Example:

Client App -> Task Router -> Web Service (Altered object)
Web Service -> Task Router -> Client App

How can I make the task router not care about class types. I really don't
want to code every possible class type into the router as new apps will also use this. Is there a method for doing what I am trying, seems there should
be a way to avoid the constant updating and maintenance.

Thanks,

Chris

[Dino Chiesa [Microsoft]]

My opinion:

Establish a baseline message type (defined in XSD) that includes an
extension of xsd:any. The router accepts the baseline and routes based on
what is typed in XSD. The senders and receivers can use any specialized
version of that baseline.

check out these references
http://www.xfront.com/ExtensibleContentModels.html
http://www.w3schools.com/schema/schema_complex_any.asp
and
http://msdn.microsoft.com/library/en...ce04162003.asp

-Dino
"AA" <[e-mail]> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

My opinion..

Use reflection for dynamic load of classes and serialization/deserialization

AA
"Chris Smith" <us**@email.com> wrote in message
news:e9*************@TK2MSFTNGP11.phx.gbl...

I bet this question has been asked quite a bit, but if someone can point me

in the right direction, I would be very grateful.

I would like to write a assembly (dll) that one of the functions will act as

a task router. This router will take different objects of many types,

and pass that object to the correct webservice for handling. Seems that doing this creates quite a bit of serialization issues, especially when the
webservice returns a modified object to the task router for forwarding to the client.

Example:

Client App -> Task Router -> Web Service (Altered object)
Web Service -> Task Router -> Client App

How can I make the task router not care about class types. I really don't want to code every possible class type into the router as new apps will

also

use this. Is there a method for doing what I am trying, seems there should be a way to avoid the constant updating and maintenance.

Thanks,

Chris