Hi Dave,
While I can't help with the "how to make Axis" part, I can guide you to get
the Headers part.
Do this... create a sample service in ASP.net, and then add some SOAP
headers to it. Plenty of examples for this already on MSDN. Then look at
the generated WSDL. This is what your AXIS WSDL needs to look like...
Hope this helps
Dan Rogers
Microsoft Corporation
--------------------
>From: "bangeye" <davecline@gmail.com>
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 7 lines]
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1103070057 3209 127.0.0.1 (15 Dec 2004
00:20:57 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Wed, 15 Dec 2004 00:20:57 +0000 (UTC)
[quoted text clipped - 3 lines]
> posting-account=jRPe9Q0AAAAe3fZ42KUHYKB1jnVk-63A
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.glorb.com!postnews.google.com!c13g2000cwb.googleg
roups.com!not-for-mail
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:27196
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 19 lines]
>Dave Cline
>~bangeye~
bangeye - 15 Dec 2004 17:24 GMT
Dan,
Thanks for your reply.
Yes I figured out that .NET will emit the SoapHeaders properly for
those services which have been decorated thusly.
And yes I could copy/paste this on to a static WSDL which had been
copied from the dynamic WSDL but this would cause maintenance problems
and I figure if AXIS is already pumping soap descriptions why can't it
do soap headers too.
I'll keep hunting and post my findings to this list.
regards,
dave cline
Dan Rogers - 15 Dec 2004 18:19 GMT
Hi Dave,
It sounds like an issue to take up with the Axis devs.
With a lot of the free tools, it is turning out to be a common practice to
keep your own (caller owned) WSDL for a remote end point. For myself, I
don't advocate exposing WSDL automatically for any production service. The
reson is you cannot change it anyhow - since it is a contract that your
clients signed up for at the time they were deployed.
Regards
Dan
--------------------
>From: "bangeye" <davecline@gmail.com>
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 9 lines]
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1103131493 29627 127.0.0.1 (15 Dec 2004
17:24:53 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Wed, 15 Dec 2004 17:24:53 +0000 (UTC)
[quoted text clipped - 4 lines]
> posting-account=jRPe9Q0AAAAe3fZ42KUHYKB1jnVk-63A
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.maxwell.syr.edu!postnews.google.com!z14g2000cwz.g
ooglegroups.com!not-for-mail
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:27216
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 12 lines]
>regards,
>dave cline