• 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

REST WS in place of SOAP

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


We have proposal to migrate from SOAP (JAXWS) to REST WS. I have few queries please clarify :-


1) Pros & Cons in REST compared to SOAP ?

2) Whether WSDL 2.0/WADL needed to provide contract based approach or is there any way to provide a contract based app. in REST?

3) Which implementor to choose Jersey, CXF , RestEasy?

4) How to debug REST WS? whether we have any tool like SOAP UI to debug REST?

5) REST webservice consumers should use REST API? We have 18 partners consuming our WS, when producing REST WS all the consumers should use the same REST API?

6) REST security as it doesn't follow WS standard, how to implement it?

Thanks & Regards,
Anantha

 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

1) Pros & Cons in REST compared to SOAP ?


The WebServicesFaq points to lots of material on this.

2) Whether WSDL 2.0/WADL needed to provide contract based approach or is there any way to provide a contract based app. in REST?


WSDL is a SOAP concept - it does not apply to REST. WADL is the way to go if you want to supply something comparable for REST WS.

3) Which implementor to choose Jersey, CXF , RestEasy?


That's up to you. The beauty of WS is that consumers do not need to care what technology is used for implementing them.

4) How to debug REST WS? whether we have any tool like SOAP UI to debug REST?


I'm not aware of something that does as much for raw HTTP as SOAP-UI does for SOAP (although I'm sure something is out there if you search for it), but then, SOAP is a LOT more complex than HTTP.

5) REST webservice consumers should use REST API? We have 18 partners consuming our WS, when producing REST WS all the consumers should use the same REST API?


Do you really care what API the clients use? If you provide them with documentation, or a WADL, they can use whatever they want to use. What benefit do you see in clients all using the same API?

6) REST security as it doesn't follow WS standard, how to implement it?


I wouldn't say REST doesn't follow any standard - there simply is no standard for REST WS like there is for SOAP WS in the shape of WS-Security. You can use anything that you might use to secure any other hTTP communication, like HTTP authentication (Basic or Digest), SSL, data encryption.
 
reply
    Bookmark Topic Watch Topic
  • New Topic