You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by John Pletka <jp...@abraxis.com> on 2006/06/18 08:20:55 UTC
Axis2 generates invalid parameters in WSDL for simple service
Perhaps I am doing something wrong, but the WSDL that Axis2 v1.0 is generating is unusable because it adds message parts that are not in the class. The same class in Axis 1.4 generates it clean.
For example, for the sample class:
public class TestAxis {
public String getDate(){
return new java.util.Date().toString();
}
}
Axis2 generates
<wsdl:message name="getDateMessage">
<wsdl:part element="ns0:getDate" name="part1" />
/wsdl:message>
<wsdl:message name="getDateResponse">
<wsdl:part element="ns0:getDateResponse" name="part1" />
</wsdl:message>
Looking at the original code, there should not be any message for the getDateMessage input. Basically it seems to assume that everything is coming in as an OEMessage data type.
This makes integration with non-axis2 clients next to impossible. For example if Visual Studio .NET 2003 points to that WSDL file, the stubs it generates require an input parameter (which the method should not require), and since it is an axis2 internal data type, nothing you put in there is accepted by the axis2 engine.
Axis1.4 generates clean wsdl from the same source that is easily called from .NET.
Is there something I'm missing here?
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 generates invalid parameters in WSDL for simple service
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Can you post the full WSDL that was generated please ? I suppose you
used Java2WSDL ?
Ajith
On 6/18/06, John Pletka <jp...@abraxis.com> wrote:
> Perhaps I am doing something wrong, but the WSDL that Axis2 v1.0 is generating is unusable because it adds message parts that are not in the class. The same class in Axis 1.4 generates it clean.
>
> For example, for the sample class:
> public class TestAxis {
> public String getDate(){
> return new java.util.Date().toString();
> }
> }
> Axis2 generates
> <wsdl:message name="getDateMessage">
> <wsdl:part element="ns0:getDate" name="part1" />
> /wsdl:message>
> <wsdl:message name="getDateResponse">
> <wsdl:part element="ns0:getDateResponse" name="part1" />
> </wsdl:message>
>
> Looking at the original code, there should not be any message for the getDateMessage input. Basically it seems to assume that everything is coming in as an OEMessage data type.
>
> This makes integration with non-axis2 clients next to impossible. For example if Visual Studio .NET 2003 points to that WSDL file, the stubs it generates require an input parameter (which the method should not require), and since it is an axis2 internal data type, nothing you put in there is accepted by the axis2 engine.
>
> Axis1.4 generates clean wsdl from the same source that is easily called from .NET.
>
> Is there something I'm missing here?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org