[
https://issues.apache.org/jira/browse/AXISCPP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530912
]
nadir amra commented on AXISCPP-429:
------------------------------------
OK, from my observations on what Java side of things does when generating Java
stubs, it seems to be that:
If input parameters exist, namespace specified for param is used
else if no input parameters exist, then the namespace for the <soap:body > is
used if it exists
else null string is used for namespace.
That will be the logic I will be using.
Thus, the else-leg code will be changing so that it looks like the following:
else
{
// Use namespace specified in input/output binding if one exists
String namespaceURI = minfo.getNamespaceURI();
if (namespaceURI == null)
namespaceURI = "";
writer.write( "\t\tm_pCall->setOperation(\""
+ minfo.getMethodname() + "\", \""
+ namespaceURI + "\");\n");
}
> generated stubs use request message name, instead of operation name for
> setOperation
> ------------------------------------------------------------------------------------
>
> Key: AXISCPP-429
> URL: https://issues.apache.org/jira/browse/AXISCPP-429
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - RPC
> Affects Versions: 1.5 Alpha
> Reporter: Adrian Dick
> Assignee: nadir amra
> Fix For: current (nightly)
>
>
> The WSDL2Ws tool generates doc/literal stubs where the setOperation method
> uses the request message name, rather than the operation name.
> Regretably, all of our tests have these values set the same, hence this
> problem never having been seen before.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
