At first i thought that it was a stupid suggestion, since the image i've got about webservices is tied to the ability to invoke methods and send objects between systems...but i think he might have a point...there's just somthing i'm not that sure about: when sending object between applications, he writes that it's not possible to send object-logic allong with the data - which seems logical, since that would requiere an extensive meta-language that would cover all possible logic for an object.
What i was wandering when i read the article was: instead of relying on the two implementations to have the same logic for the same datastructure, why not build a data-only object that could be passed as a parameter, instead of using only SOAP-messaging and sending xml-strings that each side would have to parse? That way, the two sides would know how the data is structured, and they could implement different classes that handles the data (perhaps differently), and the data-object could then be passed as a parameter between the two sides...As i see it axis would then handle the (de-)serialization of the object, and neither side would have to worry about parsing the xml-string correctly(?) ...or have i misunderstood the whole thing? :) ./Dennis [snip] > The VB author promotes the use of SOAP messaging but discourages the use > of > SOAP RPC in favor of platform specific RPC technologies. I wonder how > many > Axis users support that point of view and how many oppose it. > > http://www.learnxmlws.com/tutors/rpcmsg/rpcmsg.aspx > > > Are there any Axis users out there that want to offer an opinion? > Please [snip]
