Steve\David
Is there any way around this aside from editing the generated stub and
service.xml file. I am hitting the same issue.
cheers
</jima>
Steven E. Harris wrote:
David Illsley <[EMAIL PROTECTED]> writes:
Yes, that's my understanding.
In my testing over the weekend, I found that if I manually set the
Action to something like "urn:myMethodName", I could get my client
requests to reach the proper skeleton on the server:
,----[ Adjustment to generated stub code ]
| _operationClient.getOptions().setAction("urn:myMethodName");
`----
I also had to edit the generated Action value in my services.xml file:
,----
| <operation name="myMethodName" mep="http://www.w3.org/ns/wsdl/in-out";>
| <actionMapping>urn:myMethodName</actionMapping>
| </operation>
`----
I'm not sure where this URN usage comes from; I'd rather see the Web
Services Addressing Metadata scheme for WSDL 2.0 being used:
[target namespace]
[delimiter]
[interface name]
[delimiter]
[operation name]
[direction token]
Apparently any action string will work, so long as the same one is
supplied in the server's services.xml file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
