• Post Reply Bookmark Topic Watch Topic
  • New Topic

Expose all operations OR just one

 
Nitin Gaur
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are considering 2 approaches while exposing web services to internal applications. Please help in deciding the pros and cons of each.

Approach-1 is standard in which all operations are exposed. Client generate jaxb bindings and knows what operation to invoke and call the service accordingly. No need to provide additional documentation to client other than WSDL. But whenever WSDL is updated, client side artifacts need to be generated again to support the changes in WSDL

Approach-2 is not common in which only one operation is exposed and client generate jaxb bindings once and knows what operation to invoke, set a parameter in header and call the service accordingly. Service provider identifies the operation based on the parameter in the request header. Need to provide additional documentation (about parameter to business operation mapping) to client other than WSDL. But whenever WSDL is updated, client side artifacts need not to be generated again to support the changes in WSDL
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi again!
Personally, I feel very hesitant regarding the use of non-standard approaches such as the second approach you describe.
It may initially seem like a good idea, but my experience tells me that things tend to become complicated in the long run.
However, if you have a good motivation for your idea, then use it!
Additionally if you are considering something like the second approach, then perhaps RESTful web services would be a viable alternative?
Best wishes!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!