Practical usecase based difference between JAX-RPC vs JAX-WS vs JAX-RS web services

Question

I know there are many documents available on net which mostly describes technical difference.

But I'm rather interested to know what are the common use cases where you prefer one specific type over other any why ?

Are those preferences because integration patterns/products support particular type ?

Answer 1

Thanks for answer. However practical use case difference and when to use what. Both, JAX-WS and JAX-RS have standard implementations. I have come up with the following differences:

RESTful services (Mostly web integration, mobile phone apps)

• Integration over web will be easy with the REST. Popularly used with the AJAX calls.
• Not verbose as SOAP services so need less bandwidth hence good to use for the mobile apps.
• Web services are completely stateless so only for stateless services.

JAX-WS and JAX-RPC are SOAP based services. (Enterprise web services)

JAX-WS Java EE later versions support this and standards still evolving. - SOAP based services not preferred for mobile app communication because of heavy payload compare to rest. - More suitable for the enterprise web services where you need interoperability, transactions, message delivery and reliability.