You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "prithviraj singh (JIRA)" <ji...@apache.org> on 2010/03/29 15:27:27 UTC
[jira] Commented: (AXIS2-3199) Java2WSDL output for no parameters
or void return type
[ https://issues.apache.org/jira/browse/AXIS2-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850904#action_12850904 ]
prithviraj singh commented on AXIS2-3199:
-----------------------------------------
Is there any update on this issue.We are also facing ,almost the same issue.
our interface has the following API :
public String isCycleRunning(); (It doesn't take any input parameter).
java2wdl(doc/literal wrapped style) [Axis2 .14] generates the following WSDL
____________________________________________________________
<xs:element name="isCycleRunningResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<wsdl:message name="isCycleRunningRequest"/>
<wsdl:message name="isCycleRunningResponse">
<wsdl:part name="parameters" element="ns:isCycleRunningResponse"/>
</wsdl:message>
____________________________________________________________
but ideally it should have the following entries ,which we got using IBM soap toolkit:
____________________________________________________________
<xs:element name="isCycleRunning">
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="isCycleRunningResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<wsdl:message name="isCycleRunningRequest">
<wsdl:part name="parameters" element="ns:isCycleRunning"/>
</wsdl:message>
<wsdl:message name="isCycleRunningResponse">
<wsdl:part name="parameters" element="ns:isCycleRunningResponse"/>
</wsdl:message>
____________________________________________________________
Because the WSDL is not proper ,and when we try to generate the proxy file(cs) using wsdl to dotnet , it makes the return type as "isCycleRunningResponse " instead of "string".
public isCycleRunningResponse isCycleRunning() {
object[] results = this.Invoke("isCycleRunning", new object[0]);
return ((isCycleRunningResponse)(results[0]));
}
I guess, this is quite a serious issue and should be given high priority , otherwise we won't be able to consume the Axis2 services using .Net client.
> Java2WSDL output for no parameters or void return type
> ------------------------------------------------------
>
> Key: AXIS2-3199
> URL: https://issues.apache.org/jira/browse/AXIS2-3199
> Project: Axis2
> Issue Type: Bug
> Reporter: Deepal Jayasinghe
> Assignee: Deepal Jayasinghe
>
> Deepal,
> Per the wrapped convention, if you have the following interface:
> public String foo();
> java2wsdl should generate an input element called "foo":
> <w:message name="fooRequest">
> <w:part name="parameters" element="t:foo"/>
> </w:message>
> And "foo" must be defined as:
> <s:element name="foo">
> </s:complexType>
> </s:element>
> See the JAX-WS spec for the specific requirements of the wrapped
> convention, or my blog for a quick overview:
> http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
> Anne
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org