message headers in WSDL

[Saha Kumar]

Hello All,

How are message headers represented in a WSDL?

Thanks in advance.

-Saha

[Rizwan Mohammad]

They are not represented in wsdl file.
They are represented in server specific deployment descriptor file.
For exmaple server-config.wsdd for Axis, webservices.xml in Websphere, etc..

[Peer Reynders]

Originally posted by Rizwan Mohammad:
They are not represented in wsdl file.

Of course they are:

Each header definition gets its own <message> definition

It doesn't appear in the <portType> definition

The header message definition is then referenced inside the <binding> <input> and <output> elements (where appropriate) by a soapbind header element alongside the soapbind body element.

See at the bottom of:
MZ's SCDJWS Guide: Chapter 1. XML Web Service Standards
[ December 05, 2006: Message edited by: Peer Reynders ]

[Saha Kumar]

Thanks, Peer. Could show an example? I can't access the link you've provided. Thanks in advance.

-Saha

[Saha Kumar]

Hello All,

I have found the following link which may be useful to those interested in how message headers are represented in WSDL.

click

Regards,
Saha

[Peer Reynders]

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:soapbind="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:mh="http://www.Monson-Haefel.com/jwsbook/BookQuote"
 xmlns:mi="http://www.Monson-Haefel.com/jwsbook/message-id"
 targetNamespace="http://www.Monson-Haefel.com/jwsbook/BookQuote">
 
    <types>
        [B]<!-- this schema defines <message-id> element for the header -->[/B]
        <schema targetNamespace="http://www.Monson-Haefel.com/jwsbook/message-id"
         xmlns="http://www.w3.org/2001/XMLSchema">
            <element name="message-id" type="string"/>
        </schema> 
    </types>
 
    [B]<!-- Used to defined headers that are used with operations -->[/B]
    <message name="Headers">
        <part name="message-id" element="mi:message-id" />
    </message>
 
    <message name="getBookPrice">
        <part name="isbn" type="xsd:string" />
    </message>
 
    <message name="getBookPriceResponse">
        <part name="price" type="xsd:float" />
    </message>
 
    [B]<!-- Headers don�t appear in the portType definition -->[/B]
    [B]<!-- as it is not part of the abstract interface. -->[/B]
    [B]<!-- Handlers deal with headers -->[/B]
    <portType name="BookQuote">
        <operation name="getBookPrice">
            <input message="mh:getBookPrice"/>
            <output message="mh:getBookPriceResponse"/>
        </operation>
    </portType>
 
    <binding name="BookQuoteSoapBinding" type="mh:BookQuote">
        <soapbind:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="getBookPrice">
            <soapbind:operation style="rpc" soapAction=""/>
            <input>
                [B]<!-- Headers appear in the binding -->[/B]
                <soapbind:header message="mh:headers" part="message-id" use="literal" />
                <soapbind:body use="literal" 
                    namespace="http://www.Monson-Haefel.com/jwsbook/BookQuote"/>
            </input>
            <output>
                <soapbind:body use="literal" 
                    namespace="http://www.Monson-Haefel.com/jwsbook/BookQuote"/>
            </output>
        </operation>
    </binding>
 
    [B]<!-- This is the basis for the Java Service Interface -->[/B]
    <service name="BookPriceService">
        [B]<!-- Endpoint service interface accessor is based on the <port> element -->[/B]
        <port name="BookPrice_Port" binding="mh:BookQuoteSoapBinding" />
            <soapbind:address
                location="http://www.Monson-Haefel.com/jwsbook/BookQuote"/>
        </port>
    </service>
 
</definitions>

[Rizwan Mohammad]

Sorry all for my wrong reply.. I thought you are asking on message handlers, lately I learnt you are asking about message headers. I use soap header terminology more than message header.

[Saha Kumar]

Rizwan, no problem.

Peer, many thanks for the snippet!

-Saha