axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saminda Abeyruwan" <>
Subject Re: custom message receiver implementation
Date Tue, 16 Jan 2007 12:53:38 GMT
On 1/16/07, Nencho Lupanov <> wrote:
> Hi axis-dev team,
> I implemented a custom message receiver class extending
> AbstractInMessageReceiver<http://localhost:8080/axis2/rest/HelloWorldWS/sayHello?name=YourName>
> .
>  it is currently registred per service operation.
>  When i list the axis2 services and try to view the wsdl of a
>  particular service using that message receiver i get the following error:
>  <error>
>   <description>Unable to generate WSDL for this service</description>
>   <reason>If you wish Axis2 to automatically generate the WSDL, then
> please use one of the RPC message receivers for the service(s)/operation(s)
> in services.xml. If you have added a custom WSDL in the META-INF
> directory, then please make sure that the name of the service in
> services.xml (/serviceGroup/service/@name) is the same as in the custom
> wsdl's service name (/wsdl: definitions/wsdl:service/@name).</reason>
>   </error>
>  it seems that Axis2 cannot generate dinamically WSDL fir non-rpc message
> receivers.
>  Anyway i need to be able to access the wsdl within the the Axis2
> monitoring services,
>  so my question is:
>      Is there any workaround to show a manually added wsdl in the META-INF
>  directory of the particular service, instead of the dinamically generated
> one?

Add the wsdl to the META-INF folder. The service binding  name of the wsdl
should be the  name of  service.

thanks in advance,
>  nencho

Saminda Abeyruwan

Software Engineer
WSO2 Inc. -

View raw message