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 Michele Mazzucco <Mi...@ncl.ac.uk> on 2006/05/05 10:34:53 UTC
[Axis2 1.0] Service deployment problems
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
Re: [Axis2 1.0] Service deployment problems
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Mochele;
Your service does not have any problem and if you deploy the service
then you can invoke that too. The error you are getting is not something
make your service a faulty service, it is a decision that we took to
reduce the number of JIRA that we may get in the future:)
We can generate wsld for any given service w.o any problem , but in the
mean time if some one code gen using that wsdl he should be able to
invoke the service. So the wsdl we are generating is based on java
reflection and that assume message receiver as RPC we can not guaranty
that will work for all the message receivers. What if someone use RawXML
message receiver and try to invoke the service using generated wsdl ,
then he will fail to do so , since the auto generated wsdl does not
compatible with RawXML message receivers.
To solve those problem , we no longer auto generate the wsdl. and Axis2
only print out the wsdl in the two scenarios that Ajith mentioned.
Michele Mazzucco wrote:
>Ajith,
>
>this is non my case since I deployed my services as well services from
>the sample folder (that work on Axis2 RC4), all working with the Axis2
>primary APIs.
>
>
>Michele
>
>Ajith Ranabahu wrote:
>
>
>>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 <Mi...@ncl.ac.uk> 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
>>
>>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2 1.0] Service deployment problems
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Ajith,
this is non my case since I deployed my services as well services from
the sample folder (that work on Axis2 RC4), all working with the Axis2
primary APIs.
Michele
Ajith Ranabahu wrote:
> 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 <Mi...@ncl.ac.uk> 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
Re: [Axis2 1.0] Service deployment problems
Posted by Ajith Ranabahu <aj...@gmail.com>.
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 <Mi...@ncl.ac.uk> 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