Working on Bug #203257

I’ll be working on Bug# 203257. It falls under WTP Web Services and has a Priority level of P2 and Severity.Equals(Normal). I performed extreme research on various Web Services bugs and found this one interesting as compared to others. Below are some of the other reasons for choosing this bug:

1. Has more than enough documentation
2. Contains attachments (WSDL file)
3. Has a duplicate bug which contains additional documentation
4. The person who reported the bug resides in Toronto
5. I was easily able to reproduce this bug

Since, I’ll be dealing with Web Services Description Language (WSDL), so I refreshed my knowledge on WSDL by going through Jordan’s notes and online examples.

Below is a very good example and gives a 10,000 foot view of namespaces and attributes used in the WSDL document.

<definitions name=”HelloService”
targetNamespace=”http://www.ecerami.com/wsdl/HelloService.wsdl”
xmlns=”http://schemas.xmlsoap.org/wsdl/”
xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”
xmlns:tns=”http://www.ecerami.com/wsdl/HelloService.wsdl”
xmlns: xsd=”http://www.w3.org/2001/XMLSchema”>

The use of namespaces is important for differentiating elements, and it enables the document to reference multiple external specifications, including the WSDL specification, the SOAP specification, and the XML Schema specification.

The definitions element also specifies a targetNamespace attribute. The targetNamespace is a convention of XML Schema that enables the WSDL document to refer to itself. Above I’ve specified a targetNamespace of http://www.ecerami.com/wsdl/HelloService.wsdl. Note, however, that the namespace specification does not require that the document actually exist at this location; the important point is that you specify a value that is unique, different from all other namespaces that are defined.

Finally, the definitions element specifies a default namespace: xmlns=http://schemas.xmlsoap.org/wsdl/. All elements without a namespace prefix, such as message or portType, are therefore assumed to be part of the default WSDL namespace.

WSDL Elements

• <types> The data types used by the web service
• <message> The messages used by the web service
• <operation> The action supported by the web service
• <portType> The operations performed by the web service
• <binding> The communication protocols used by the web service
• <port> The particular network address for a binding
• <service> The collection of related endpoints (ports)

The example I’ve used above was taken from this source.