> How about using either an XML string or an
> XML Element as the input parameter.
> This way the client programs do not have
> to worry about the custom classes. What I
> did was to use an XML Element as the input
> parameter to the SOAP service. And on
> the server, extract the values from the
> Element into custom classes. The client
> only needs to know the structure of the
> XML element and you don't need to worry
> about distributing the custom classes.
We're using exactly the same thing (XML Elements), and they turn out to
be a pretty neat solution. If you use a DTD/Schema to specify the format
of the XML, you only have to worry about redistributing the Schema.
Dealing with XML Elements of course does ask for DOM parsing capability
in the code, though. And that can end up being a performance issue.
Using an XML String, would allow you to use SAX, and fix the performance
problems, but then coding time would shoot up.
Any better suggestions?
--
Rajesh J Advani
-----------------------------------
Intolerance will not be tolerated!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
