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

Web Services best practices

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello-

I just learned the basics of Web Services a few days ago. I've successfully created a web service around some very basic code and exposed it via the WSDL file. I've also written a client application that consumes this service. We're using Java 1.4, Tomcat 4.1 and Axis.

Now that I have the basics down, I've got some questions:

1. Where can I find some best practices for documenting the exposed WS methods to the consumer?

2. What is the best way to ensure backward compatibile code in the case that one of my APIs needs to change? Is it standard practice to write a wrapper around the code you want to expose?

3. Feel free to throw in any other considerations I should keep in mind.

Thanks!

Aaron
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic