Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > avoiding XML serialization, different WSDL generation, soap serialization

Reply
Thread Tools

avoiding XML serialization, different WSDL generation, soap serialization

 
 
Ramunas Urbonas
Guest
Posts: n/a
 
      07-20-2004
Hello,

I think my problem is interesting for most of developers who wish to
exchange actual business entities with webservices, not just xml stubs.

I can not use XML serialization, when generating wsdl, because some of
transmited entities have only getters. It is required by our framework and
cannot be avoided (to ensure data consistency in most cases).

How do I exchange business entities in that case? I found several solutions,
basically they all imply serializing my classes with soap/binary formatters
and passing parameters as XmlElements, strings or byte arrays. That implies:
1. versioning problems (but that can be avoided with extra work),
2. anonymous parametes (any serialized object will be passed as
XmlElement, or any other selected transfer type. Type validation will be
performed only during run time, which leads to bugs).
3. using XML serialization either way, just ussing "always XML
serializable" format for parameters.

How else could this problem be addressed? Suggestions are very welcome..

regards,
Ramunas Urbonas


 
Reply With Quote
 
 
 
 
Dino Chiesa [Microsoft]
Guest
Posts: n/a
 
      07-27-2004
Rather than transmitting the actual entities, have you considered using an
Adapter (GoF 139) or Visitor (331) or Memento (283) ?

-D

"Ramunas Urbonas" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> I think my problem is interesting for most of developers who wish to
> exchange actual business entities with webservices, not just xml stubs.
>
> I can not use XML serialization, when generating wsdl, because some of
> transmited entities have only getters. It is required by our framework and
> cannot be avoided (to ensure data consistency in most cases).
>
> How do I exchange business entities in that case? I found several

solutions,
> basically they all imply serializing my classes with soap/binary

formatters
> and passing parameters as XmlElements, strings or byte arrays. That

implies:
> 1. versioning problems (but that can be avoided with extra work),
> 2. anonymous parametes (any serialized object will be passed as
> XmlElement, or any other selected transfer type. Type validation will be
> performed only during run time, which leads to bugs).
> 3. using XML serialization either way, just ussing "always XML
> serializable" format for parameters.
>
> How else could this problem be addressed? Suggestions are very welcome..
>
> regards,
> Ramunas Urbonas
>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
SOAP::WSDL, wsdl2perl and soap 1.2 Me Perl Misc 2 04-09-2010 08:00 AM
how to move from java object serialization to xml serialization? Dimitri Ognibene Java 4 09-02-2006 07:32 AM
Object serialization XML vs java serialization plasticfloor@gmail.com Java 3 06-14-2006 03:45 AM
Avoiding De-Serialization Mark Oueis ASP .Net Web Services 7 12-16-2004 07:29 PM
is the w3c's schema for wsdl and wsdl/soap binding possibly buggy ? _clb_ Chris Bedford XML 0 08-20-2003 11:52 PM



Advertisments