• 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 ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

rpc and soap attachments

Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could anyone please offer some advice on the following ? I'm using apache tomact and axis, but if you know of other tools that can do what I need, it would also be of great help.
Thanks a lot in advance.
Is there an easy way to configure high-level tools to serialize binary info, like images, into *soap attachments* ?
By "high level tools" I mean tools that allow you you code only logic, and not worry about soap and xml. On the client side it's the stub automatically generated by wsdl2java. On the server side: apche rpcrouter, or axis/services, or whatever tool you use to automatically deploy a provider class.
Eg, suppose my web service returns Employee objects, containing a name and a binary image. I'd like the image part to be passed as a soap attachment.
Now, I *do* understand how to:
1) Write explicit code to send/receive soap message + attachments.
However, that's dirty low-level work, requiring you to directly code soap.
2) Alternatively, use those "high level tools" and tell them to register a special serializer/deserializer for images.
However, I don't think it uses soap *attachments* - does it ? I've made a test - created a wsdl with attachments and ran apache's wsdl2java on it. It didn't issue any errors, but I got the impression it completely ignored attachments.
So, my question:
3) Is there a third way - an easy way to tell those high tools that my employee images should be serialized into soap *attachments* ?
Thanks again
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic