• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Henry Wong
Saloon Keepers:
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Frits Walraven

soap serialization (newbie?)

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
How do I inform clients about the serialization technique my SOAP server can understand. One way could be to use WSDL and mention a Java class for serialization and one for deserialization, I think. This though, does not seem general enough. How would clients download the classes? What if the clients are not Java clients at all. In that case how can I de-serialize the client request parameters?
Thanks and regards
M Faruqui

 
Ranch Hand
Posts: 782
Python Chrome Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The whole point of Web Services is to achieve interoperability.
You cannot think solely in terms of java-java endpoints.
 
m faruqui
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

That is what I dont get
The call parameters have to be converted to XML. There are many ways of doing that. The big question - how do I tell clients what technique they should use to convert parameters to XML? And how to ensure that they will be able to interpret the XML response that the server sends.
Thanks
 
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
http://www.w3.org/TR/2001/WD-soap12-20010709/#_Toc478383512 http://xml.apache.org/soap/faq/#faq_topic_serialization

------------------
My ramblings @
http://javarecon.tripod.com
 
Ranch Hand
Posts: 464
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by m faruqui:

That is what I dont get
The call parameters have to be converted to XML. There are many ways of doing that. The big question - how do I tell clients what technique they should use to convert parameters to XML? And how to ensure that they will be able to interpret the XML response that the server sends.
Thanks


It is my understanding you stick to the SOAP standards and the encoding over the wire, there by the client who picks up your services will use they own way or implementation to get the message from the back-end webservices..
Currently, there are lots of interoperability issues that are on-going betn java and .net world..
http://www.xmethods.net/ilab/ilab.html
Ragu
 
It's exactly the same and completely different as this tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic