JDK6:何时使用捆绑的JAX-WS实现与Project Metro [英] JDK6: when to use bundled JAX-WS implementation versus Project Metro

查看:64
本文介绍了JDK6:何时使用捆绑的JAX-WS实现与Project Metro的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

JAX-WS实现可用于提供Web服务服务器,而无需任何其他库. JVM将以指定端口上的WS服务器启动.

JAX-WS implementation bundled with JDK6 can be used to provide a web services server without any additional libraries. JVM will start with a WS server on a specified port.

https://www.oracle.com/technical-resources/articles/javase/jax-ws-2.html

http://java.sun.com/developer/technicalArticles/J2SE/jax_ws_2_pt2/

我的问题是,这与Metro项目有什么不同?如果最终目标是在tomcat中托管Web服务,那么我是否仍可以使用捆绑功能,然后直接重定向到此捆绑的ws服务器,还是部署Metro servlet更好?

The question I have is how does this differ from project Metro? If the end goal is to host web services inside tomcat, then can I still use bundled functionality and then just redirect to this bundled ws server or is it better to deploy the metro servlet?

推荐答案

据我所知,JAX-WS只是一个模板,必须由JDK6或Metro实现来实现.

As far as I know JAX-WS is only a template which has to be implemented by either the JDK6 or the Metro implementation.

Metro仅是Glassfish Application Server随附的标准实现. 请参阅此处.

Metro just is the standard implementation shipped with the Glassfish Application Server. See here.

因此应该没有任何差异.

Therefore there shouldn't be any differences.

这篇关于JDK6:何时使用捆绑的JAX-WS实现与Project Metro的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆