I see a couple things wrong in your SOAP Header entry:
1- The <soap:Header> element name is case sensitive. It must be
<soap:Header>, not <soap:header>.
2- All SOAP Header entries must be namespace qualified.
But -- per the specification, there is no requirement that the SOAP
Header entry must be a complexType with child elements. In fact, the
SOAP 1.1 spec shows the following example:
<SOAP-ENV:Header>
<t:Transaction
xmlns:t="some-URI" SOAP-ENV:mustUnderstand="1">
5
</t:Transaction>
</SOAP-ENV:Header>
Nonetheless, if .NET can't process a simple type, then I recommend
that you define your header entry as a complexType.
Anne
On 7/2/05, Amit <[EMAIL PROTECTED]> wrote:
> Hi All,
> I have deployed a web service using AXIS and I am able
> to access the same without any problems from a Java
> client. I was trying to access the same using .NET
> client and I ran into some issues which created doubts
> regarding structure of soap header. I am using
> following header
> <soap:header><Version>1.0</Version></soap:header>
> Is this a valid header accroding to soap? I am not
> able to create the same using .NET. It seems that you
> can only create the headers that have other elements
> and no values.
> E.g. <A><B>abc</B><C>ab</c></A>. Could not put any
> value for the element A. E.g <A>ABC</A>.
>
> Please let me know if anyone has encountered such
> problem before and any pointers would be very useful.
>
> Thanks in Advance,
> Amit
>
>
>
>
> ____________________________________________________
> Yahoo! Sports
> Rekindle the Rivalries. Sign up for Fantasy Football
> http://football.fantasysports.yahoo.com
>
