jax-ws vs axis2 - 需要帮助 [英] jax-ws vs axis2 - help needed
问题描述
我需要以下帮助：
Q.1） -
之间的性能比较1）包含基于jax-ws的Web服务的大量war文件部署在Jetty
2）部署在在Jetty上运行的axis2上的大量Web服务
Q.1) Performance comparison between - 1) lot of war files containing jax-ws based web services deployed on Jetty 2) lot of web services deployed on axis2 running on Jetty
Q.2）此外，如果有许多类型的客户端，例如。基于net，java，c ++，它们将使用这些Web服务然后我应该使用哪种方法 - axis2作为SOAP引擎或jax-ws ??
Q.2) Also, if there are many types of clients, like .net, java, c++ based, which are gonna use these web services then which approach should I go with - axis2 as SOAP engine or jax-ws??
Q.3如果我对WS- *标准不感兴趣那么我应该使用axis2还是jax-ws？
Q.3) if I am not interested in WS-* standards then what should I use axis2 or jax-ws?
Q.4）一般来说为什么需要SOAP引擎？仅适用于WS- *标准支持或者它们对它们有更多好处???
Q.4) In general why are SOAP engines required?? only for WS-* standard support or do they have more benefits to them???
推荐答案
用于XML Web服务的Java API（ JAX-WS）只是一个API。
Java API for XML Web Services (JAX-WS) is just an API.
您需要使用SOAP堆栈实现（SOAP引擎）。
You need to use a SOAP stack implementation (SOAP engine).
有两个主要的实现：
- Axis2
- Metro
由于Metro提供了参考实现并且随JDK一起提供，我认为你一直在调用jax-ws到RI 。但是metro是一个完整的SOAP Stack实现。
Since Metro provides the Reference Implementations and is shipped with JDK, I assumed you have been calling jax-ws to the RI. But metro is a full SOAP Stack implementation.
现在你现在知道你的名字和地点，你就可以开始寻找你最喜欢的实现了。两者都有利有弊。
请记住，两者都为您提供WS- *标准支持，并且由于SOAP独立于编程语言与客户端类型无关。
Now you that you now the names, and the places, you can start your quest for your favorite implementation. Both have pros and cons. Keep in mind that both provide you the WS-* standards support, and since SOAP is "programing language independent" doesn't matter the client types.
我个人更喜欢Metro，因为它更容易使用。
I personalty prefer Metro, since it is much more easer to use.
这篇关于jax-ws vs axis2 - 需要帮助的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
