Vinh is using XmlBeans (Java) for serialization. I think that what you say is true for any data binding framework - if you're using another language on the client, you'll need to make sure it has some kind of equally-powerful data binding framework to translate the XML into the language's own structures. Regardless of what you use, the XML is standards-compliant and does not require Java to parse.
Dan Balan Subramanian/Raleigh/[EMAIL PROTECTED] wrote on 12/07/2006 05:24:10 AM: > The only concern I have about this is the use of XStream for serializing > complex types. If XStream is not used on both sides, non-Java clients have > to deserialize the XML put on the wire (which is XStream specific) to the > corresponding form the fundamental issue being the serialization XStream > does is not standard. > > Balan Subramanian > Autonomic Computing, IBM, RTP, NC > 919.543.0197 | [EMAIL PROTECTED] > > > > > > > "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> > 12/07/2006 02:32 PM > Please respond to > [email protected] > > > To > <[email protected]> > cc > > Subject > Muse and non-java client > > > > > > > Just to confirm...can a non-java client be used to interact with Muse? > > I am pretty sure yes because even though Muse is a java implementation, > it is also a web service that communicates with remote applications via > the standard XML format. Much of the current clients are java > applications, although I see no reason why a perl or other non-java > client can't talk to a Muse-based application. As long as the non-java > clients have APIs to easily work with the XML received from Muse, and > return it in proper XML format to Muse, the client should work. For > example, Perl should work, but if no existing web service APIs are > available for Perl, it would just be more difficult to build a > Perl-based client at this time. Correct? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
