Research on the WebService Passing Objects Based on JAX-WS
Some people think that Tango is a different stack than our JAX-WS RI stack.
So, sometimes, to make this point in email messages, we've been saying "JAX-WS RI + Tango".
JAX-WS knows how to do web services stuff, but it doesn't know how to do schema stuff.
Create and define the service class as a Spring bean using a JAX-WS front end.
As mentioned earlier, JAX-WS relies on JAXB to handle the data binding for most of its Web services content.
Add a TextView element with the id "springmessage" to display the JAX-WS web service response for a method call to one of the get methods.
It is important to know that the service interface's method arguments, return types, and exceptions must conform to JAX-WS and EJB specifications.
It's designed as a light-weight SOAP processing engine (though as with JAX-WS 2.0, Axis2 also includes some support for REST) which is extensible in many different ways.
I am running out of room here to describe those, so let me point to a tutorial about them and mention that I quite like them, especially how they are applied to the JAX-WS provider programming model.
Although at this point documentation, web sites etc. will continue to refer to the old names and the Metro binary is the Tango binary, including the JAX-WS RI.
这稍微有些偏题，您可以参考 相关的教程；另外还要指出的是，我非常喜欢这些东西，特别是其应用到JAX-WS 提供者编程模型的方式。
