Return-Path: 
 <axis-user-return-22989-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 85485 invoked from network); 1 Apr 2004 18:58:44 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 1 Apr 2004 18:58:44 -0000
Received: (qmail 69079 invoked by uid 500); 1 Apr 2004 18:58:25 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 68915 invoked by uid 500); 1 Apr 2004 18:58:24 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 68903 invoked from network); 1 Apr 2004 18:58:24 -0000
Received: from unknown (HELO mx02.lexis-nexis.com) (207.25.178.45)
  by daedalus.apache.org with SMTP; 1 Apr 2004 18:58:24 -0000
Received: from mailgate2.lexis-nexis.com (mailgate2.lexis-nexis.com
 [138.12.44.45])
	by mx02.lexis-nexis.com (8.12.10/8.12.10) with ESMTP id i31Ivx4g026826
	for <axis-user@ws.apache.org>; Thu, 1 Apr 2004 13:57:59 -0500
Received: from LNXDAYEXCH01.lexis-nexis.com (lnxdayexch01.lexis-nexis.com
 [138.12.13.32])
	by mailgate2.lexis-nexis.com (8.12.9/8.12.9) with ESMTP id i31IwRA1011406
	for <axis-user@ws.apache.org>; Thu, 1 Apr 2004 13:58:27 -0500
Received: by lnxdayexch01b.lexis-nexis.com with Internet Mail Service
 (5.5.2657.72)
	id <HZQB7CMD>; Thu, 1 Apr 2004 13:58:27 -0500
Message-ID: 
 <42B8643373BD554EBBF2AA0AEA8776000A1C3E40@lnxdayexch01b.lexis-nexis.com>
From: "Hodgeman, Robert (LNG-DAY)" <Robert.Hodgeman@lexisnexis.com>
To: "'axis-user@ws.apache.org'" <axis-user@ws.apache.org>
Subject: Explicit SOAP headers and WSDL2Java
Date: Thu, 1 Apr 2004 13:58:26 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MIMEDefang 2.38
X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

I've done extensive searching on this subject, turning up a lot of questions
but few answers.  Most of the questions/answers were regarding implicit
headers and WSDL2Java's failure to support them (in the past, I understand
that they are supported now).

I have an operation defined in my wsdl that requires a header element in the
request message (for a service I provide).  I understand how to get my
handler to extract and interpret the header element, but am unable to find
any trace of the header element in my WSDL2Java generated stubs.  There is a
statement on one of the axis pages on wiki.apache.org that "The WSDL2Java
generation tool will recognize these [explicit] headers in most cases and
emit stub classes that include the headers are arguments to the methods."
Obviously a client can use the Stub interface to insert an arbitrary header,
but that sort of defeats the purpose of having the definition in the WSDL.

I am not finding this to be the case, and suspect that I do not have my WSDL
defined entirely properly.  Here is a snippet of WSDL that shows what I
have, I'm hoping someone can shed some light on the problem.  I am using
Axis 1.1 final's WSDL2Java tool:

First, the schema that defines the header I want to use is imported:
<types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
        <import namespace="http://security.common.mydomain.com"
schemaLocation="Security.xsd" />
    </schema>
</types>

Next, I define the header message and part I'm trying to use:
<message name="MyAppHeaders">
    <part name="SecurityToken" element="security:SecurityToken" />
</message>

The portType is specified, just showing the input and output body elements
(defined/imported in the same file, but omitted here as irrelevant):
<portType name="MyPort">
    <operation name="MyOperation">
        <input message="tns:MyInputMessage"/>
        <output message="tns:MyOutputMessage"/>
    </operation>
</portType>

Later, I define my binding, specifying the header element I want to use:
<binding name="MySoapBinding" type="tns:myPort">
    <operation name="MyOperation">
        <soap:operation soapAction="MyOperation_v1"/>
        <input>
            <soap:header use="literal" message="tns:MyAppHeaders"
part="SecurityToken"/>
            <soap:body use="literal">
        </input>
        <output>
            <soap:body use="literal">
        </output>
    </operation>
</binding>

My understanding is that headers defined explicitly in the WSDL in this
manner should show up somewhere in the genereated stubs.  Is that not the
case?  My goal here is obviously to include the header information in the
WSDL to allow the WSDL to describe the header element that is expected, as
opposed to the client just having to "know" that it is expecting a header
element.

Thanks very much in advance for any advice.  I'm hoping that I included
enough detail here that someone will be able to at least tell me if I'm
completely off base with my expectations or if it's just an error in the
wsdl on my part.

-Bob