JAX-RPC与JAX-WS与JAX-RS Web服务之间基于实际用例的区别 [英] Practical usecase based difference between JAX-RPC vs JAX-WS vs JAX-RS web services

问题描述

我知道网上有很多文件可以用来描述技术差异.

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 ?

推荐答案

感谢您的回答.但是实际用例有所不同，什么时候使用什么. JAX-WS和JAX-RS都有标准实现.我提出了以下差异:

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服务(主要是Web集成，手机应用程序)

• 通过REST可以轻松实现Web集成.广泛用于AJAX调用.
• 不像SOAP服务那样冗长，因此需要较少的带宽，因此很适合用于移动应用程序.
• Web服务是完全无状态的，因此仅适用于无状态服务.

JAX-WS和JAX-RPC是基于SOAP的服务. (企业网络服务)

JAX-WS Java EE更高版本支持此功能，并且标准仍在不断发展. -基于SOAP的服务不是有效的移动应用程序通信，因为有效负载比较重. -更适合需要互操作性，事务，消息传递和可靠性的企业Web服务.

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.

这篇关于JAX-RPC与JAX-WS与JAX-RS Web服务之间基于实际用例的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！