Query regarding RPC/Document Style,WSGEN and WSIMPORT

[Jolly Tiwari]

Hi! everybody,

I have a query regarding the style attribute in the binding element in WSDL.
I created a SOAP based service using both RPC style and DOCUMENT style one by one.

FINDINGS

1.After executing wsgen on Implementation class in both the cases i found that no source or class file was created in case of RPC style.


2.in case of Document style , i found two source and class files corresponding to the function name,like getDateAsString and getDateAsStringResponse.

3.after executing wsimport ,in case of document style ,i found again two classes(getDateAsString and getDateAsStringResponse.
) along with proxy classes.

DOUBTS

1.when and why are these classes (getDateAsString and getDateAsStringResponse) required?

2.I was able to run this soap based document style web service without running wsgen and wsimport through a POJO java client code.In that case how and when are these two mentioned classes (getDateAsString and getDateAsStringResponse) created?

3. After invoking without any proxy and associated classes i tried after running wsimport and using those generated classes.it was successfull.but again i found that these two classes (getDateAsString and getDateAsStringResponse)were created.so why should we run wsgen when we can get the same classes generated through wsimport?


I request all here to explain the requirement of all this in simple words as i have went through many documents which use heavy words like translation of java types to XML and such stuff but I am not able to get it.

Thanks in advance

Regards

Jolly

[Ivan Krizsan]

Hi!
How about letting us have a look at the WSDL you use?
You can, for instance, comment the parts that differ for RPC and Document style.

[Jolly Tiwari]

I am sharing WSDL's in both the cases i.e RPC and DOCUMENT style respectively

 <?xml version="1.0" encoding="UTF-8" ?> 
- <!--  Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6. 
  --> 
- <!--  Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6. 
  --> 
- <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://trial1.docstyle/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://trial1.docstyle/" name="EndInterfaceImplService">
  <types /> 
  <message name="getDateAsString" /> 
- <message name="getDateAsStringResponse">
  <part name="return" type="xsd:string" /> 
  </message>
- <portType name="EndInterface">
- <operation name="getDateAsString">
  <input message="tns:getDateAsString" /> 
  <output message="tns:getDateAsStringResponse" /> 
  </operation>
  </portType>
- <binding name="EndInterfaceImplPortBinding" type="tns:EndInterface">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" /> 
- <operation name="getDateAsString">
  <soap:operation soapAction="" /> 
- <input>
  <soap:body use="literal" namespace="http://trial1.docstyle/" /> 
  </input>
- <output>
  <soap:body use="literal" namespace="http://trial1.docstyle/" /> 
  </output>
  </operation>
  </binding>
- <service name="EndInterfaceImplService">
- <port name="EndInterfaceImplPort" binding="tns:EndInterfaceImplPortBinding">
  <soap:address location="http://127.0.0.1:9876/testdoc" /> 
  </port>
  </service>
  </definitions>

**********************

 <?xml version="1.0" encoding="UTF-8" ?> 
- <!--  Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6. 
  --> 
- <!--  Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6. 
  --> 
- <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://trial1.docstyle/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://trial1.docstyle/" name="EndInterfaceImplService">
- <types>
- <xsd:schema>
  <xsd:import namespace="http://trial1.docstyle/" [b]schemaLocation="http://127.0.0.1:9876/testdoc?xsd=1"[/b] /> 
  </xsd:schema>
  </types>
- <message name="getDateAsString">
  <part name="parameters" element="tns:getDateAsString" /> 
  </message>
- <message name="getDateAsStringResponse">
  <part name="parameters" element="tns:getDateAsStringResponse" /> 
  </message>
- <portType name="EndInterface">
- <operation name="getDateAsString">
  <input message="tns:getDateAsString" /> 
  <output message="tns:getDateAsStringResponse" /> 
  </operation>
  </portType>
- <binding name="EndInterfaceImplPortBinding" type="tns:EndInterface">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
- <operation name="getDateAsString">
  <soap:operation soapAction="" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
  </binding>
- <service name="EndInterfaceImplService">
- <port name="EndInterfaceImplPort" binding="tns:EndInterfaceImplPortBinding">
  <soap:address location="http://127.0.0.1:9876/testdoc" /> 
  </port>
  </service>
  </definitions>

for schemaLocation="http://127.0.0.1:9876/testdoc?xsd=1"

[b] <?xml version="1.0" encoding="UTF-8" ?> 
- <!--  Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6. 
  --> 
- <xs:schema xmlns:tns="http://trial1.docstyle/" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0" targetNamespace="http://trial1.docstyle/">
  <xs:element name="getDateAsString" type="tns:getDateAsString" /> 
  <xs:element name="getDateAsStringResponse" type="tns:getDateAsStringResponse" /> 
- <xs:complexType name="getDateAsString">
  <xs:sequence /> 
  </xs:complexType>
- <xs:complexType name="getDateAsStringResponse">
- <xs:sequence>
  <xs:element name="return" type="xs:string" minOccurs="0" /> 
  </xs:sequence>
  </xs:complexType>
  </xs:schema>[/b]

This all i am able to see after executing my simple piece of code and then putting http://127.0.0.1:9876/testdoc?WSDL in the browser:

package docstyle.trial1;

import javax.xml.ws.Endpoint;

public class Publisher
{    

public static void main(String...a)
{
Endpoint.publish("http://127.0.0.1:9876/testdoc",new EndInterfaceImpl());
}
}

Regards

Jolly

[Ivan Krizsan]

Hi!
Here are some quick attempts at answers, for the time being:
1. With Document style services, the contents of the SOAP body is a custom XML fragment that can be validated.
JAX-WS, using the JAXB XML schema compiler, generates JAXB bean classes aiding in binding XML data to a tree of Java objects. In this case, the tree representing a request and a response is just one single object.
When using RPC, no such JAXB classes are needed, since you only use simple type (string) parameters and return data in your methods.
In the case of RPC, the root of the XML element in the SOAP body typically is an element with the same name as the web service operation (method) invoked. This is not described in any XML schema, but is a convention for RPC.
2. Strictly speaking, the JAXB bean classes need not to be created, since SOAP messages can be assembled using, for instance SAAJ.
They may be created at runtime.
3. This is the part which I want to investigate a little more.
Basically, wsgen and wsimport creates artifacts for server respective client side. The JAXB bean classes are identical on both sides.
Best wishes!

[Jolly Tiwari]

When using RPC, no such JAXB classes are needed, since you only use simple type (string) parameters and return data in your methods.

What i understood from this statement is that we can work with only built in types in XML schema as request parameters and return types.
In case my method receives a user defined data type (like a Address class created by the developer) I can't go for RPC style and document style is the only option left.


Regards

Jolly

[Ivan Krizsan]

What i understood from this statement is that we can work with only built in types in XML schema as request parameters and return types.
In case my method receives a user defined data type (like a Address class created by the developer) I can't go for RPC style and document style is the only option left.

It is dead-simple to try if your statement is true or not - Create a RPC style web service that receives an user-defined data type.
I can reveal the answer right now: You can still use RPC style with user-defined data types. JAXB classes will be generated and used, as needed.
Best regards!

[Ivan Krizsan]

Hi!
I just want to correct a statement I made earlier:

Basically, wsgen and wsimport creates artifacts for server respective client side.

This is not true.
wsgen generates portable artifacts for both client and server side from an annotated web service endpoint implementation class.
wsimport generates portable artifacts from a WSDL file.
Sorry about the error.

[Abayomi Osamiluyi]

am finding it difficult to create a client for a web service created in coldfusion. I know the language in which the web service was implemented doesnt really matter.

Can anyone please show me the steps of creating the client from how to generate the artifacts using wsimport to using the artifacts to communicate with the service.

Thank you in anticipation.....