AXIS vs JAX-WS for Web Service Client [英] AXIS vs JAX-WS for Web Service Client

问题描述

我决定用Java实现Web Service Client。我在Eclipse中生成了Axis客户端，在wsimport中生成了JAS-WS客户端。这两种解决方案都有效，现在我必须选择一种解决方案。在选择一个之前我应该​​考虑什么？

I am deciding on the implementation of Web Service Client in Java. I've generated Axis client in Eclipse and JAS-WS client with wsimport. Both solutions work and now I have to choose one to go forward. What should I think about before picking one over the other?

推荐答案

JAX-WS的客户端是标准Java的一部分API和参考实现是可靠且高效的，而Axis需要第三方依赖。如果你不需要Axis实现的任何功能而不是JAX-WS提供的功能，我真的没有理由为什么你应该选择Axis而不是JAX-WS。

The client side of JAX-WS is part of the standard Java API, and the reference implementation is reliable and performant, while Axis requires 3rd party dependencies. If you don't need any functionality implemented by Axis and not offered by JAX-WS, I really don't see any reason why you should opt for Axis and not for JAX-WS.

这篇关于AXIS vs JAX-WS for Web Service Client的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！