Hi,
The WSDL generation functionality has changed for 1.0 since the WSDL
generation had a flaw. Unless you have the WSDL inside the META-INF of
the aar file, the WSDL is not auto generated except for the special
situation where the message receiver is the RPCInOutMessageReceiver.
The reason for this is that the java2wsdl code generator assumes the
service to be rpc when generating the WSDL and if the user has any
custom message receiver installed everything gets screwed up!
Ajith
On 5/5/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Hi all,
it seems there are some problems to deploy services on Axis2 1.0 (or at
least into the web browser console): all services but the version.aar
one show a message like this
<error>
<description>Unable to generate WSDL for this service</description>
<reason>
Either user has not dropped the wsdl into META-INF or operations
use
message receivers other than RPC.
</reason>
</error>
instead of the WSDL file (please try with groovyService, available into
the userguide dir, for example).
Michele
--
Ajith Ranabahu
