This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The choice between SOAP WS and RESTful WS depends on how strongly you want the contract between the consumer and producer to defined.
If your WS is intented for B2B exchanges and can be used potentially by other external companies I would go for SOAP which strongly
defined the contract via WSDL.
If your WS is intented for internal use only in your company and the interface is simple enough like in your case, there is no
need for the SOAP overhead and I would go for RESTful WS.
I discarded here the social type of B2B integration where for example the MSN website calls the Facebook RESTful API to display
you facebook status in MSN. That's a particular case.
SCJP 5 , SCWCD 5, SCEA 5
Joined: Oct 21, 2008
I have just downloaded 10 min ago my assignment and it is teamdoctor as well !
I guess I'll be facing the same design issue as you