rpc和document的区?/span>
2008-10-24 18:48:07| 分类Q?/span> webservice|字号 订阅
译?The Difference Between RPC and Document Style WSDL rpc和document到底是什么意思？他们如何?encoded/literal"相关联？二者的冲突来自哪里Q?/p> binding的style和use 通常情况下，web服务是由一个wadl文g来描q的的。在q个文g中，抽象的描q所支持的web服务操作和消息，然后兌C个具体的|?/p> l歇息和消息格式。典型的wsdl文gp个几个元素组?tyoes,message.porttype用来描述抽象的定?biding和service指定具体的实 现。所有的q些元素包装在definitions元素中?/p> 在binding元素中，rpc和document是最值得我们x的元素。wsdl ?binding描述了如何将service兌到消息协议；q些消息协议?/p> httpQmimeQsoap中的L一U。不q，实际中，soap是最常用的协议；rpc和document的区别也是在soap的下的区别（it is SOAP that the RPC/document distinction refers toQ。通常http(s)是传输soap消息的协议?/p> <wsdl:binding>元素包含一对参敎ͼstyle(rpc|document)和use(encoded|literal)Q他俩会影响到soap消息的格?他们的用方式如?/p> Q?/p> <wsdl:binding name="Config1Binding" type="prt0:CreditLimitLocalWebServiceVi_Document"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> <wsdl:operation name="creditLimitCheck"> <soap:operation soapAction="" /> <wsdl:input> <soap:body use="literal" parts="parameters" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> style属? wsdl1.1要求binding的style要么是rpc要么是doucment。这个选择与如何组lsoap的负L兟뀂下面是分别他们如何影响<soap:body>?/p> 容的l节?/p> documentQ?lt;soap:body>的内容由定义?lt;wsdl:type>中的xml模式指定。他不需要遵循特定的soap规范。简a之，soap消息是通过 <soap:body>中的document发送出去，而没有额外的要遵循的格式规则。document style是一U默认的选择?/p> rpcQ?<soap:body>元素的结构需要遵循特定的规则Qsoap1.1规范W?部分有细节）。根据这些规则，<soap:body>可以包含唯一一个元?/p> Q这个元素在operation后被命名Q所有的参数都必d成这个元素的子元素?/p> 因ؓ可以自由的选择哪种消息格式Q遵循document格式的soap消息看上d像rpc格式?/p> 现在Q决定性的问题是：选择其中L一个选项后的l果是什么样Qؓ何要选择rpc或者documentQ很多情况下Q选择他们后，soap消息 的格式看h很相像，那么Z么还要提供这U选择呢？原因要从soap标准化的历程中寻找?/p> use属?/p> q个属性指定了soap消息的编码规则。他同样?lt;wsdl:binding>元素中完成。他的gؓencoded或者literal. 他引用了一pd规则Qsoap客户端和soap服务端都遵@q些规则以解?lt;body>元素中的内容?/p> use="literal" 意味着type定义遵@xml模式定义 use="encoded" 参考xml中已有的应用数据Q通常指的是soap1.1规范中的soap~码规则。如果文档中没有自定义数据，可以选择 encoded?/p> 附文章全文： The Difference Between RPC and Document Style WSDL Summary RPC style and document style are catchphrases frequently heard in the context of web services and the SOAP protocol. What exactly do they mean? How do they relate to the pair of terms "encoded/literal"? Where does the confusion about these terms come from? This article describes the WSDL binding style and use attributes. By Susanne Rothaug 20 Nov 2004 Binding Style and Use A web service is usually described by a WSDL (Web Services Description Language) document. In this document, the supported web service operations and messages are described abstractly and then bound to a concrete network protocol and message format. A typical WSDL document consists of the following elements: "types," "message," and "portType" for the abstract definitions; "binding" and "service" for the concrete specification. All of these elements are wrapped inside a "definitions" element. In the context of RPC and document style, it is the binding element that we need to take a closer look at. A WSDL binding describes how the service is bound to a messaging protocol, either HTTP GET/POST, MIME, or SOAP. In practice, SOAP is the most universally used protocol; it is SOAP that the RPC/document distinction refers to. Usually HTTP(S) is used as transport protocol for the SOAP message – "SOAP over HTTP(S)." The <wsdl:binding> element of the WSDL contains a pair of parameters that influence the form of the resulting SOAP messages: binding style (RPC or document) and use (encoded or literal). See how style and use are defined in the WSDL fragment below: <wsdl:binding name="Config1Binding" type="prt0:CreditLimitLocalWebServiceVi_Document"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> <wsdl:operation name="creditLimitCheck"> <soap:operation soapAction="" /> <wsdl:input> <soap:body use="literal" parts="parameters" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> The "Style" Attribute WSDL 1.1 specifies the style of the binding as either RPC or document. This choice corresponds to how the SOAP payload - i.e., how the contents of the <soap:Body> element - can be structured. Here are some details of how each style affects the contents of <soap:Body>:
As a consequence of the freedom of choice that the document style offers, the SOAP messages conforming to a document style WSDL may look exactly the same as the RPC equivalent. The decisive question now is: What are the consequences of choosing one option or another? Why choose RPC over document, or document over RPC? In many cases, the SOAP messages generated from either RPC or document style WSDLs look exactly the same - so why offer the choice at all? The reason may be found in the history of the SOAP standard. SOAP has its roots in synchronous remote procedure calls over HTTP and the appearance of the document accordingly followed these conventions. Later, it was seen as a simplification to use arbitrary XML in the SOAP body without adhering to conventions. This preference is reflected in the document style WSDL documents. So far, both options are represented in the WSDL specification and the choice of one or the other is mainly a question of personal taste since most SOAP clients today accept both versions. The "Use" Attribute The use attribute specifies the encoding rules of the SOAP message. This is also done within the <wsdl:binding> element, as seen in the example above. The value can be encoded or literal. It refers to the serialization rules followed by the SOAP client and the SOAP server to interpret the contents of the <Body> element in the SOAP payload.
The combination of the style and use attributes leads to four possible style/use pairs:
Some of these combinations are rarely used in practice, such as document/encoded. In general, the literal use is gaining importance, and as far as RPC/encoded is concerned, the Web Services Interoperability Organization (WS-I) in its Basic Profile Version 1.0a of August 2003 ruled out the use of SOAP encoding with web services. Document/literal and RPC/literal will be the only allowed style/use combinations in the future. |
]]>
1. Generate KeyStore
set SERVER_DN="CN=Server, OU=ec, O=ec, L=nanchang, S=jiangxi, C=CN"
set SERVER_DN="CN=Server, OU=ec, O=ec, L=nanchang, S=jiangxi, C=CN"
set CLIENT_DN="CN=Client, OU=ec, O=ec, L=nanchang, S=jiangxi, C=CN"
set KS_PASS=-storepass PASSWORDHERE
set KEYINFO=-keyalg RSA
keytool -genkey -alias Server -dname %SERVER_DN% %KS_PASS% -keystore server.keystore %KEYINFO% -keypass strongit
keytool -export -alias Server -file test_axis.cer %KS_PASS% -keystore server.keystore
keytool -import -file test_axis.cer %KS_PASS% -keystore client.truststore -alias serverkey -noprompt
keytool -genkey -alias Client -dname %CLIENT_DN% %KS_PASS% -keystore client.keystore %KEYINFO% -keypass strongit
keytool -export -alias Client -file test_axis.cer %KS_PASS% -keystore client.keystore
keytool -import -file test_axis.cer %KS_PASS% -keystore server.truststore -alias clientkey -noprompt
2. Modify server.xml
3. add below code into your invoke code
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
clientAuth="false" keystoreFile="D:\test\server.keystore" keystorePass="PASSWORDHERE"
truststoreFile="D:\test\server.truststore" truststorePass="PASSWORDHERE" sslProtocol="TLS" />
3. add below code into your invoke code
System.setProperty("javax.net.ssl.keyStore",
"D:\\test\\client.keystore");
System.setProperty("javax.net.ssl.keyStorePassword", "PASSWORDHERE");
System.setProperty("javax.net.ssl.trustStore",
"D:\\test\\client.truststore");
System.setProperty("javax.net.ssl.trustStorePassword",
"PASSWORDHERE");
URL url = new URL("https://localhost:8443/TOMCAT6/services/GetName");
]]>
04:03:33,714 INFO [STDOUT] java.rmi.ServerException: EJBException:; nested exception is:
javax.ejb.EJBException: Invalid invocation, check your deployment packaging, method=public abstract test.ejb.TestEJBInterface test.ejb.TestEJBHome.create() throws javax.ejb.CreateException,java.rmi.RemoteException
解决办法Q?/span>
1] Edit conf/jboss-service.XML and make CallByValue as 'true' in NamingService as below
<mbean code="org.jboss.naming.NamingService"
name="jboss:service=Naming"
xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
true
2] Edit deploy/ear-deployer.xml, and set Isloated and CallByValue as true
3]Edit deploy\jbossweb-tomcat55.sar\META-INF\jboss-service.xml , and set Java2ClassLoadingCompilance and UseJbossWebLoader attributes as false
]]>
一、环境准?/font>
1.1软g下蝲准备
Tomcat 5.5下蝲地址Q?br />
http://tomcat.apache.org/download-55.cgi#5.5.20
Axis War包：
http://ftp.wayne.edu/apache/ws/axis2/1_1_1/axis2.war
Axis Eclipse plug-in(代码生成工具和打包工?Q?br />
http://apache.justdn.org/ws/axis2/tools/1_1_1/axis2-eclipse-codegen-wizard.zip
http://apache.justdn.org/ws/axis2/tools/1_1_1/axis2-eclipse-service-archiver-wizard.zip
Eclipse 3.2Q?br /> http://www.eclipse.org/
MyEclipse5.5M1Q?br /> http://www.myeclipseide.com/
1.2安装
A.首先搭徏开发环境，下载的Eclipse解压~到一个目录，D:eclipse-SDK-3.2-win32?br /> B.下载到?/span>Axis 的两?/span>plug-in解压~到D:Axis-Plugin-Direclipseplugins目录?/span>?br /> C.在eclipse目录下创建D:eclipse-SDK-3.2-win32eclipselinksQ新建文件名?axis-eclipse-plugin.link
内容为：
path=D:Axis-Plugin-Dir
D.安装MyEclipse5.5M1,eclipse目录指向D:eclipse-SDK-3.2-win32Q删除D:eclipse-SDK-3.2-win32eclipseconfiguration下的org.eclipse.update目录?span lang="">然后启动
2、Web Servieces plugins
E.下面开始搭建Web Services的部|环境?br />
下载的tomcat5.5解压~到一个目录D:Tomcat5.5?/p>
F.axis2.war包拷贝到tomcat安装目录下的webapps目录?/p>
G.启动Tomcat(D:Tomcat5.5binstartup.bat)Q打开览器输入ƈ讉K:http://127.0.0.1:8080/axis2 来查?l果如下图，表示axis2已经工作正常?/p>
二、快速开?/p>
2.1创徏webApps目
启动MyEclipseQ新建立一?/span>WebAppsQ?/span>File->New->Project->Web ProjectQ?/span>,l?/span>Project Name ?/span>SayHelloQ其他保持不改变?br />
2.2创徏WSDL文g
A.选择File->New-Other菜单Q进入后扑ֈMyEclipse->Web Servicesq择WSDL.如下图：
B.点击下一步按钮，昄如下图：
C.选择“src”目录作ؓ“Enter or select the parent folder”的|“File name”值给定ؓSayHello.wsdl?/font>
D.下一步》所有界面内容取默认|FinishQ?/font>
E.昄WSDL设计器的界面如下Q?/span>
F.修改图中标红色的部分Q?br />
修改图中的NewOperation为SayHello;
修改input中parameters为SayHelloRequest;
修改output中parameters为SayHelloResponse;
修改完后如下图：
U色框内为变化的内容QWSDL文g修改完毕?/span>
2.3?/span>WSDL生成Java代码
A.选择菜单“File->New->Other”Q从对话框中选取“Axis2 Wizards”下面?#8220;Axis2 Code Generator”.点击“Next”
B.q入下一个页面，保持“Generate java source code from WSDL file”被选中Q点?#8220;Next”q入下一步?/span>
C.点击“Browse”来选取存放?/span>src目录下的SayHello.wsdl文gQ?#8220;Next”q入下一步?br />
D.首先生成客户端代码和试代码Q设|如下：
E.下一步后Q选择SayHellosrc目录Q如下图Q?br />
Finish !
F.重复从A到C的步骤，然后生成服务端代码，讄如下Q?br />
后面同E?/span>
G.l束后，h目Q如图：
q是׃没有Axis2?/span>jar包放?/span>class path 中以及源代码?/span>package不ؓorg.example.www.sayhello引v的?br />
H.修改包名为org.example.www.sayhelloq从tomcat中的axis2 web应用WEB-INF/lib目录中加载所?/span>jar包到目的classpath中?/span>
I.?font size="4" face="楷体_GB2312">SayHelloTest.java 中引?/font>junit包?/font>
2.4~写业务代码
打开SayHelloSKeleton.java文g其中的方法如下：
public org.tonyzhangcn.ws.sayhello.SayHelloResponse SayHello(org.tonyzhangcn.ws.sayhello.SayHelloRequest param0)
{
// Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
{
// Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
修改为：
public org.tonyzhangcn.ws.sayhello.SayHelloResponse SayHello(org.tonyzhangcn.ws.sayhello.SayHelloRequest request)
{
try {
{
try {
SayHelloResponse response = new SayHelloResponse();
response.setOut("Hi,"+request.getIn()+".How are you?");
return response;
}catch(UnsupportedOperationException e)
{
throw e;
}
}
}
2.5打包
A.选择菜单“File->New->Other”Q从对话框中选取“Axis2 Wizards”下面?#8220;Axis2 Services Archive”.点击“Next”q入下一个页?/span>?/span>
B.选择~译好的class文g所在目录（本项目应该是WebRoot下面WEB-INF/classesQ，“Next”q入下一步?/span>
C.选择WSDL文g所在目录，此处?/span>src目录下的SayHello.wsdl文g?#8220;Next”,?#8220;Next”。选择services.xm文g?/span>
D.点击“Next”Q将记入最后一个页面，此处有两个选项Q一个是输出目录一个是处处文g名称。这里的输出文g名称l的?/span>SayHello。点?#8220;Finish”完成?/span>
2.6部v
AQ将打包好的文gSayHello.jar拯?/span>Tomcat中已l部|的Axis2应用?/span>WEB-INF/services目录下面?/span>
B.重新启动Tomcat?/span>
C.打开览器，输入http://127.0.0.1:8080/axis2,q点d中的“services”链接可以看到SayHello已经被部|Ӏ点?/span>SayHello提供的连接可以看C之对应的WSDL?/span>
2.7调用试
A.修改SayHelloTest.java文g中的ҎtestSayHello的内容ؓQ?br />
public void testSayHello() throws java.lang.Exception {
String url="http://localhost:8080/axis2/services/SayHello";
org.example.www.sayhello.SayHelloStub stub = new org.example.www.sayhello.SayHelloStub(url);
org.example.www.sayhello.SayHelloStub.SayHello request = (org.example.www.sayhello.SayHelloStub.SayHello) getTestObject(org.example.www.sayhello.SayHelloStub.SayHello.class);
request.setIn("Teamlet");
System.out.println(stub.SayHello(request).getOut());
assertNotNull(stub.SayHello(request));
}
org.example.www.sayhello.SayHelloStub stub = new org.example.www.sayhello.SayHelloStub(url);
org.example.www.sayhello.SayHelloStub.SayHello request = (org.example.www.sayhello.SayHelloStub.SayHello) getTestObject(org.example.www.sayhello.SayHelloStub.SayHello.class);
request.setIn("Teamlet");
System.out.println(stub.SayHello(request).getOut());
assertNotNull(stub.SayHello(request));
}
从菜单中选择“RunQ?/span>>Run as->JUnit Test 完成试Q?/font>
<EOF>
]]>