• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WSDL file questions

 
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi everyone,

i got a list of WSDL files, and my manager ask me to understand WSDL file and write a report which describe what information we could get from these files.

since i am new to WSDL files, and my concerns here are "what i need to write in my report in order to give whatever my manager ask for"


thank you,
 
Ranch Hand
Posts: 2198
1
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!
If you have bare WSDL files, without any comments, then this is probably what you will be able to extract from them:
- Addresses of the different endpoints.
- What service is made available at which address.
- WHat kind of transport medium is used to communicate with the service (example: HTTP, which also is the most common).
- The operations made available by each service.
- What indata and outdata (both optional) each operation accepts and produces.

I think this is everything. If there are comments or descriptions, then all the better - perhaps the comments will provide additional information.
Best wishes!
 
jim li
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
@WebService(name = "ICCClaimServiceInterface", targetNamespace = "http://aaa.com/ICCClaimService")
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@XmlSeeAlso({
ObjectFactory.class
})
public interface ICCClaimServiceInterface {


@WebMethod(operationName = "GetClaimLifeCycleState", action = "http://ICCClaimService/GetClaimLifeCycleState")
@WebResult(name = "GetClaimLifeCycleStateResponse", targetNamespace = "http://aaa.com/ICCClaimMessages", partName = "response")
public GetClaimLifeCycleStateResponse getClaimLifeCycleState(
@WebParam(name = "GetClaimLifeCycleStateRequest", targetNamespace = "http://aaa.com/ICCClaimMessages", partName = "request")
GetClaimLifeCycleStateRequest request);

- Addresses of the different endpoints.
where can i find this based on the information above?

- What service is made available at which address.
where can i find this based on the information above?

- WHat kind of transport medium is used to communicate with the service (example: HTTP, which also is the most common).
where can i find this based on the information above?

- The operations made available by each service.
getClaimLifeCycleState

- What indata and outdata (both optional) each operation accepts and produces.
inputobject - GetClaimLifeCycleStateRequest
outputobject - GetClaimLifeCycleStateResponse


thank you

 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!
You haven't provided a WSDL, just an annotated Java interface.
There is not much to say from that, except what you already have inferred.
Best wishes!
 
jim li
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
<definitions
xmlns:tns="http://test.com/DisclosuresService"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:msgs="http://test.com/DisclosuresMessages"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://test.com/DisclosuresService" name="DisclosuresService"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<xsd:schema>
<xsd:import schemaLocation="DisclosuresMessages.xsd"
namespace="http://test.com/DisclosuresMessages"
id="msgs"/>
</xsd:schema>
</types>
<message name="MessageIn">
<part name="request" element="msgs:RenderPDFRequest" />
</message>
<message name="MessageOut">
<part name="response" element="msgs:RenderPDFResponse" />
</message>
<message name="MessageException">
<part name="exception" element="msgs:RenderExceptions" />
</message>

<message name="UpdatePackageShippedDetailsFromCDSIn">
<part name="request" element="msgs:UpdatePackageShippedDetailsFromCDSRequest" />
</message>
<message name="UpdatePackageShippedDetailsFromCDSOut">
<part name="response" element="msgs:UpdatePackageShippedDetailsFromCDSResponse" />
</message>

<portType name="DisclosuresInterface">
<operation name="renderPDF">
<input message="tns:MessageIn" />
<output message="tns:MessageOut" />
<fault name="Exception" message="tns:MessageException" />
</operation>
<operation name="updatePackageShippedDetailsFromCDS">
<input message="tns:UpdatePackageShippedDetailsFromCDSIn" />
<output message="tns:UpdatePackageShippedDetailsFromCDSOut" />
</operation>
</portType>

<binding name="DisclosuresBinding" type="tns:DisclosuresInterface">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="renderPDF">
<soap:operation soapAction="" style="document" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<fault name="Exception">
<soap:fault name="Exception" use="literal" />
</fault>
</operation>

<operation name="updatePackageShippedDetailsFromCDS">
<soap:operation soapAction="" style="document" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
</binding>

<service name="DisclosuresService">
<port name="DisclosuresPort" binding="tns:DisclosuresBinding">
<soap:address location="http://test2:1111/Curam/DisclosuresService" />
</port>
</service>
</definitions>
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!

- Addresses of the different endpoints.
where can i find this based on the information above?


In the <service> element:

http://test2:1111


- What service is made available at which address.
where can i find this based on the information above?


Again, in the <service> element. Your service only has one single endpoint, thus there can only be one service exposed.
Look at the binding attribute in the <port> element in the <service> element - it says "DisclosuresBinding".
Then locate the <binding> element higher up in the WSDL that has a name attribute with the name "DisclosuresBinding". The very same <binding> element has a type attribute, that specifies the "interface" the service exposes. In this case it is the "DisclosuresInterface".
The interface of the web service is specified in the <portType> element a little higher up in your WSDL.
Best wishes!
 
jim li
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
thank you very much for the help
reply
    Bookmark Topic Watch Topic
  • New Topic