Hi Michael,
I hope you are using Message style service here.
I don't how to add this to axis client. But u can edit your SOAP message
directly if you are using tcpmon. So in tcpmon add another element(your
operation name)directly under soap body. For some reason axis client is not
doing this(if you find please let me know too :)).
For eg: if you look into your tcpmon, you can see under soap body, your
document is appended directly with out a wrapper element.
<soapenv:Body>
<your document>
</soapenv:Body>
so edit it like this...
<soapenv:Body>
<your-method-name>
<your document>
</your-method-name>
</soapenv:Body>
then resend tcpmon.
This way you can invoke any method in your webservice. Unfortunately I don't
know to write an axis client for this.
Hope this helps(Not a complete answer, but partial).
Cheers,
Ranjith Pillai.
-----Original Message-----
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 1:47 PM
To: Axis User mailing list
Subject: How to define document/literal service with multiple operations
How can I define a document/literal service with multiple operations?
Because
there's no wrapper element around the input message parts, Axis seems to
have a
problem invoking the correct service method.
If I add a value for SOAPAction in the service's binding, the client stubs
set
SOAPAction in the HTTP request correctly, but Axis doesn't use the
SOAPAction
value. I found the Axis HTTPActionHandler class and tried adding it to the
request flow in the service's deploy.wsdd but it didn't seem to make a
difference. Does Axis support this? If so, how do I configure it?
Thanks,
Mike
--
Mike Woinoski Pine Needle Consulting
mailto:[EMAIL PROTECTED]
