axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ya Bing, Chen" <>
Subject RE: weird wsdl generation in axis2
Date Sat, 07 Oct 2006 11:12:00 GMT
I c.. I will check the wsdl file again. thanks a lot!

Btw, in some cases Axis2 generated error info when I try to look at the generated wsdl. the
error is as follows:
   <description>Unable to generate WSDL for this service</description>
      Either user has not dropped the wsdl into META-INF or operations use message receivers
 other than RPC.

does it mean I have to use rawxml message receiver if I want Axis2 to generate the wsdl?
but I am wondering what is the difference between RPC receiver and rawxml one? 
actually even after I changed to use RPC receiver in services.xml (org.apache.axis2.rpc.receivers.RPCMessageReceiver),
the error remains there.  

-----Original Message-----
From: Srinath Perera []
Sent: Fri 10/6/2006 7:02 PM
Subject: Re: weird wsdl generation in axis2
Reason is diffent default styles in Axis2 and Axis1.x

Axis1.x have rpc-encoding as default style .. so it have something
like <part type="MyType"> on the otherhand Axis2 does doc-literal
where you will have

<part element = "addElement"> and
 in your schema

<elemement name="addElement" type="xsd:int"/>

1) This is not a bug
2) doc-literal style is preferred over rpc-encoding

On 10/6/06, Ya Bing, Chen <> wrote:
> Hi all,
> I started to use axis2 recently. But find out it is very strange with
> the generated wsdl.
> When I deploy my ws (*.aar), then try to take a look at the generated
> wsdl from the admin console.
> Axis2 seems always generated weird and wrong wsdl for my service.
> For example, I deploy an calculator ws. The input and output method's
> arguments are int.
> But when I look at the wsdl, the generated ones become like the
> following:
> <wsdl:message name="addMessage"/>
> <wsdl:message name="addResponse"/>
> <wsdl:message name="substractMessage"/>
> <wsdl:message name="substractResponse"/>
> There supposed to be some parts elements such as: <wsdl:part name="in0"
> type="xsd:int"/> in the generated wsdl.
> Then I tried to drop my own wsdl inside the aar. Unfortunately, the
> axis2 seems cannot recognize it.
> I was using Axis1.x before, never encounter such errors. Don't know if
> it is bugs or some configuration errors.
> Anyone encounter the same issues as me? Pls help!
> Regards,
> Yabing
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Srinath Perera:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message