You can drive it even further and not only look at it as a set of operations but real objects (instances of a classes with methods) This depends on the AXIS2/Java session scope used and it workes for me nicely in SCOPE=SOAPSESSION. If your class is not static (or sigelton) AXIS2 created me after all the mess I had very nicely one instance per session/thread which can then act as place-holder-object to invoke i.e. operations on a OpenVMS processes. That way I keep the link from a Users-Session (a user can have more then one session) all the way allong to a unique legacy process per session which runs i.e. under the users account on a OpenVMS host. The other thing is the granularity of parameters. A parameter to such a method can be a quite complex sopa document. in our case we transfer in one document in the body part 3 collections called workspaces where each workspace is a collection of field-name / field-value pairs (or tripples, quadrupples) of strings. As collections are dynamic in length, adding a name/value pair more does not require any regeneration of code. That gives us very much silence to change,a nd it maps nicely. (NOTE: AXIS2/C does not support scope=sopasession) Josef Stadelmann@ axa-winterthur.ch
-----Ursprüngliche Nachricht----- Von: Hoda, Nadeem [USA] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2008 09:30 An: [email protected] Betreff: WS Best Practice I have recently heard that one operation (method/function) per service (WSDL) is a best practice for SOA/web services. Can anyone corroborate this? I can see it being cleaner at the WSDL level, but as you expand your service offerings it will be a maintenance/client headache with dozens of WSDLs/services for no apparent reason. Also, are there good, reliable web service "best practices" guides? Thanks, Nadeem
