WSDL

彻底理解webservice SOAP WSDL

WSDL 详解

http://www.cnblogs.com/hujian/p/3494064.html

http://www.cnblogs.com/hujian/p/3497127.html

使用 WSDL 部署 Web 服务: 第 1 部分

使用 WSDL 部署 Web 服务,第 2 部分: 简单对象访问协议(SOAP)

使用 WSDL 部署 Web 服务,第 3 部分: SOAP 互操作性

SOAP Action Header


How does a simple WSDL file look?
There will be a portType element that is like an interface definition of the web-service. It would tell us :

  1. What type of input is expected and what output would be returned.
  2. Any headers they would be a part of the input/output messages.
  3. Faults generated if any.

There would be a binding element associated with the port type. Its like an implementation of the port type. It would give message format and protocol details:

  1. That the protocol used is SOAP.
  2. The message style - Document/RPC.
  3. The transport mechanism - HTTP/ SMTP.
  4. In case of SOAP, a SOAP action to help identify each of the operations.

The final component is the service element. It tells the web service clients

  1. where to access the service,
  2. via which port
  3. how the messages are defined.

The above information is represented in a port element. Each port elements is associated with a binding.
So why would a service have multiple port elements ? Why would you provide two ways to use the same operation to your clients?
The question is equivalent to "Why would an interface have two implementations ?" The one word answer to the two question would be - alternatives.
Maybe you have two versions of your web-service - Providing two ports in the service - say a OPERATION_NEW_PORT and OPERATION_OLD_PORT will allow the client to decide which of two implementations suit his need.
Maybe we need to provide transport layer variations - an HTTP version as well as an SMTP version. So an email client as well as an HTTP client could use the service. 
Maybe you have varied implementations - a bare bones implementation for internal users and a more complex system (involving auditing, header checks etc) for external world users.
Or I just want to provide multiple endpoints (who is gonna stop me !!)
The point is there is a very good chance that the web-service will have to support multiple ports. I decided to add a new port to the random service
I first defined a new binding (or a new implementation of the portType):

<wsdl:binding name="SampleServiceOperationsPortTypeSoap_V2"
type="tns:SampleServiceOperationsPortType">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="random">
<soap:operation soapAction="/Service/random/V2" />
<wsdl:input name="GetRandomRequest">
<soap:body use="literal" />
</wsdl:input> <wsdl:output name="GetRandomResponse">
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

This binding is same as the existing binding (except for the name of course). The next step would be to update the service element:

<wsdl:service name="SampleServiceOperationsPortTypeSoap">
<wsdl:port binding="tns:SampleServiceOperationsPortTypeSoap"
name="SampleServiceOperationsPortTypeSoap">
<soap:address location="randomService" />
</wsdl:port> <wsdl:port binding="tns:SampleServiceOperationsPortTypeSoap_V2"
name="SampleServiceOperationsPortTypeSoap_V2">
<soap:address location="randomServiceV2" />
</wsdl:port>
</wsdl:service>

Here I now have two port elements - each associated with a different binding. I could also have associated the two with the same binding.
The most important part is the address element of the soap namespace. One port is exposed at "randomService" and the other is exposed at "randomServiceV2"
I decided to execute a wsdl2java (CXF) on the wsdl file. The dummy server class I received was for one of the ports only - the first one. So I decided to complete the implementations.
First the interface:

@WebService(targetNamespace = "http://ws.com/Service/samplews-ns", name = "SampleServiceOperationsPortType")
@XmlSeeAlso({ ObjectFactory.class })
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
public interface SampleServiceOperationsPortType{
/**
   * Returns a random value from the application
   *
   */ @WebResult(name = "GetRandomResponse",
targetNamespace = "http://ws.com/Service/xsd/random-schema", partName = "GetRandomResponse")
public GetRandomResponse random(
@WebParam(partName = "GetRandomRequest",
name = "GetRandomRequest", targetNamespace = "http://ws.com/Service/xsd/random-schema")
GetRandomRequest getRandomRequest); }

As seen the interface has exactly one operation - getRandom which is exposed by two endpoints. The old version is:

@javax.jws.WebService(serviceName = "SampleServiceOperationsPortTypeSoap",
portName = "SampleServiceOperationsPortTypeSoap", targetNamespace = "http://ws.com/Service/samplews-ns",
wsdlLocation = "random.wsdl",
endpointInterface = "com.ws.service.samplews_ns.SampleServiceOperationsPortType")
public class SampleServiceOperationsPortTypeImpl implements SampleServiceOperationsPortType { private static final Logger LOG = Logger.getLogger(SampleServiceOperationsPortTypeImpl.class.getName()); @Override
@WebMethod(action = "/Service/random")
public GetRandomResponse random(final GetRandomRequest getRandomRequest) {
LOG.info("Executing operation random - OLD VERSION !!!");
try {
final GetRandomResponse _return = new GetRandomResponse();
_return.setValue((int) (Math.random() * 165));
return _return;
} catch (final java.lang.Exception ex) {
ex.printStackTrace();
throw new RuntimeException(ex);
}
}
}

I manually added the second endpoint:

@javax.jws.WebService(serviceName = "SampleServiceOperationsPortTypeSoap",
portName = "SampleServiceOperationsPortTypeSoap",
targetNamespace = "http://ws.com/Service/samplews-ns", wsdlLocation = "random.wsdl",
endpointInterface = "com.ws.service.samplews_ns.SampleServiceOperationsPortType")
public class SampleServiceOperationsPortTypeImplV2 implements SampleServiceOperationsPortType { private static final Logger LOG = Logger.getLogger(SampleServiceOperationsPortTypeImplV2.class.getName()); @Override
@WebMethod(action = "/Service/random/V2")
public GetRandomResponse random(final GetRandomRequest getRandomRequest) {
LOG.info("Executing operation random - NEW VERSION !!!");
try {
final GetRandomResponse _return = new GetRandomResponse();
_return.setValue(-101);
return _return;
} catch (final java.lang.Exception ex) {
ex.printStackTrace();
throw new RuntimeException(ex);
}
}
}

As seen above the two classes implement the same webservice. The two endpoints have different soap action headers. Hence the WebMethod annotation has been placed not in the interface but in the implementation class.
If we were to test the two operations by posting our requests to the two URLs the different web services would be called.
An interesting thought that came to mind is, since the two endpoints differ in SOAP Action can we get them to have the same URL ? Would CXF use a combination of URL and SOAP Action header to uniquely identify the endpoint ? 
The expectation would be that when a request is received at the operation address, CXF would check the SOAPAction header to decide where the URLs must be redirected to. 
Accordingly I modified my endpoint beans to use the same URL:

<jaxws:endpoint id="randomWs_V1"
implementor="com.ws.service.samplews_ns.SampleServiceOperationsPortTypeImpl"
endpointName="SampleServiceOperationsPortTypeSoap" address="randomService" />
<jaxws:endpoint id="randomWs_V2"
implementor="com.ws.service.samplews_ns.SampleServiceOperationsPortTypeImplV2"
endpointName="SampleServiceOperationsPortTypeSoap_V2" address="randomService" />

The elements differ in their values for the endpointName attribute. This maps to the value of the port in the wsdl service element.
While the theory seemed fine (to me), the application failed at start up:

8135 [localhost-startStop-1] ERROR org.springframework.web.context.ContextLoader
- Context initialization failed
org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'randomWs_V2': Invocation of init method failed;
nested exception is javax.xml.ws.WebServiceException:
java.lang.RuntimeException: Soap 1.1 endpoint already registered on
address randomService

The Server was least interested in the Soap Action header. A few days later I had an opportunity to attend a training session on web services at our office. The trainer cleared my queries regarding SOAP Action header as:

"This is not a SOAP Header but a HTTP Header. It is therefore not a part of the SOAP but the underlying transport layer. Hence it is not strongly coupled to SOAP implementation by SOAP web services provider. Because of its separation from the SOAP envelope its use is strongly discouraged"

I guess that kind of makes sense.

WSDL的更多相关文章

  1. webService学习之路(三):springMVC集成CXF后调用已知的wsdl接口

    webService学习之路一:讲解了通过传统方式怎么发布及调用webservice webService学习之路二:讲解了SpringMVC和CXF的集成及快速发布webservice 本篇文章将讲 ...

  2. CXF:根据werservice代码生成WSDL(转)

    原文:http://hongyegu.iteye.com/blog/619147,谢谢! import org.apache.cxf.tools.java2ws.JavaToWS; import ne ...

  3. WebServices:WSDL的结构分析

    WSDL(Web Services Description Language,Web服务描述语言)是为描述Web Services发布的XML格式.W3C组织没有批准1.1版的WSDL,但是2.0版本 ...

  4. cxf webservice 生成wsdl方法参数名称为arg0问题

    在通过cxf生成webservice服务时,如果你是用ServerFactoryBean,那么在生成wsdl时,方法的参数名称会被自动命名为arg0,arg1...,如: <xsd:comple ...

  5. cxf WebService设置wsdl中soapAction的值

    用cxf开发一个WebService很简单,只需要下面几步: 1.定义接口 public interface HelloService { String hello(); } 2.实现 public ...

  6. 彻底理解webservice SOAP WSDL

    WebServices简介 先给出一个概念 SOA ,即Service Oriented Architecture ,中文一般理解为面向服务的架构, 既然说是一种架构的话,所以一般认为 SOA 是包含 ...

  7. vs2013 手动生成webservice代理类wsdl

    第一步: 第二步: 第三步: 至此wsdl代理类生成成功!

  8. Atitit wsdl的原理attilax总结

    Atitit wsdl的原理attilax总结 1.1. 在 W3C 的 WSDL 发展史1 1.2. 获取wsdl,可能需要url后面加wsdl,也可能直接url1 1.3. Wsdl的作用2 1. ...

  9. C# 调用WebService的3种方式 :直接调用、根据wsdl生成webservice的.cs文件及生成dll调用、动态调用

    1.直接调用 已知webservice路径,则可以直接 添加服务引用--高级--添加web引用 直接输入webservice URL.这个比较常见也很简单 即有完整的webservice文件目录如下图 ...

  10. 理解WebService SOAP WSDL

    WebServices简介 先给出一个概念 SOA ,即Service Oriented Architecture ,中文一般理解为面向服务的架构, 既然说是一种架构的话,所以一般认为 SOA 是包含 ...

随机推荐

  1. Laravel 5 基础(十二)- 认证

    Laravel 出厂已经带有了用户认证系统,我们来看一下 routes.php,如果删除了,添加上: Route::controllers([ 'auth' => 'Auth\AuthContr ...

  2. js控制文本框只能输入数字 及 常用字符对应ASCII码值

    方法一: <INPUT TYPE='text' NAME=text onkeypress="a()"><script language=javascript> ...

  3. STM32F0xx_PWR低功耗配置详细过程

    Ⅰ.概述 今天总结PWR部分知识,请看“STM32F0x128参考手册V8”第六章.提供的软件工程是关于电源管理中的停机模式,工程比较常见,但也是比较简单的一个实例,根据项目的不同还需要适当修改或者添 ...

  4. JS实现浏览器的title闪烁

    经常可以看见的title里面的消息提示,下面是JS的一种实现方法:主要是通过setTimeout方法设置一个定时器,切换消息提示,从而达title到消息提示的闪烁. <html> < ...

  5. WPF之旅(二)- XAML

    什么是XAML XAML(Extensible Application Markup Lanaguage的简写,发音“zammel”)是用于实例化.NET对象的标记语言.尽管XAML是一种可以用于诸多 ...

  6. WPF动画 storyboard

    <Window x:Class="StoryBoard.MainWindow" xmlns="http://schemas.microsoft.com/winfx/ ...

  7. char const*, char*const, const char *const的区别

    C++标准规定,const关键字放在类型或变量名之前等价的.所以,const char*和 char const*是一样的. const char*   //常量指针---指向常量的指针----指针指 ...

  8. 基于AppCan MAS系统,如何轻松实现移动应用数据服务?

    完成一个移动应用开发,前端提供页面展示,当它要与一些业务系统进行交互,又该如何实现呢?2016AppCan移动开发者大会上,AppCan前端开发经理杨庆,分享了AppCan轻松实现移动应用数据服务的方 ...

  9. OpenStack: 安装准备

    >安装准备1. 安装MySQL# apt-get install python-mysqldb mysql-server将/etc/mysql/my.cnf修改bind-address为&quo ...

  10. 从零开始学ios开发(一):准备起航

    首先介绍一下自己的背景,本人09年研究生毕业,大学就不介绍了,反正是上海的一所211大学,学的是计算机科学与技术专业,学生时代,从事过ACM,没有什么太大的成就,中国的牛人是在太多,我的水平,估计连高 ...