Menu
In what contexts is it better to use one over the other and why?
Thanks!
813
Actually,JAX-WS represents both RESTful and SOAP based web services. One way to think about it is that JAX-RS specializes in RESTful, while JAX-WS allows you more flexibility to choose between either, while at the same time being (in some cases) more complicated to configure. Thank you for simple explanation.
One of the main difference between JAX-RPC and JAX-WS is the programming model. A JAX-WS based service uses annotations (such @WebService) to declare webservice endpoints. Use of these annotations obviates the need for deployment descriptors.
JAX-RS is a standard defined in Java Specification Request 311 (JSR-311) and Jersey / RESTEasy are implementations of it.
JAX-RS is a JAVA based programming language API and specification to provide support for created RESTful Web Services. Its 2.0 version was released on the 24th May 2013. JAX-RS uses annotations available from Java SE 5 to simplify the development of JAVA based web services creation and deployment.
JAX-WS is an API for SOAP-based WS, and using it for RESTful WebServices is not the best way to go about things.
So if you're looking to implement a RESTful WebService, use JAX-RS .
131
I feel like Web services are mostly tied for UDDI type applications. REST is just a plain evolution to make stateless http protocol to stateful thing by using http method communications for doing CRUD operations. Like mapping operations to methods GET, PUT, POST and DELETE.
Web Services are into coding for Airplane ticket reservation systems, Online banking, payment gateways, etc. Where there are a set of standard systems expose their API in some definitions. The JAX-RS is for providing some light weight layer for resources...
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
