This week's book giveaway is in the Agile and other Processes forum.
We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line!
See this thread for details.
The moose likes Web Services and the fly likes web service operation best practice Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "web service operation best practice" Watch "web service operation best practice" New topic
Author

web service operation best practice

ross bertolonoi
Greenhorn

Joined: Nov 24, 2008
Posts: 6
Hi everyone
I need your advise on general Webservice interface design.

Basically I need to know if I should have one operation with a parameter called rule as input and then the web-service impl will decide what kind of logic to execute based on the value of the rule parameter or have multiple operations for each rule?
For instance :
One single operation
myoperation(String rule, ....) and rule can have values such as rule1, rule2 . The WS impl will look at the value of the rule and execute some logic.
vs .
Having multiple operations
myoperationForRule1(...)
myoperationForRule2(...)
....


Thanks
Ross
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: web service operation best practice
 
Similar Threads
Session Maintenanace in Web Services
Issue with namespaces while consuming a service
Web Service question - Need your suggestion.
Parameter substitution for namespaces does not work?
Axis: Multiple methods in style="message" service?