You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/06/08 16:08:25 UTC

[jira] Resolved: (AXIS2-2739) Issue in using custom MessageReceiver, got error "Unable to generate WSDL for this service"

     [ https://issues.apache.org/jira/browse/AXIS2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas resolved AXIS2-2739.
-------------------------------------

    Resolution: Fixed

> Issue in using custom MessageReceiver, got error "Unable to generate WSDL for this service"
> -------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2739
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2739
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.1.1
>         Environment: Embedded Tomcat 5, Windows 2000
>            Reporter: Ravindra
>            Assignee: Deepal Jayasinghe
>            Priority: Critical
>
> I created service using Spring beans and configured org.apache.axis2.rpc.receivers.RPCMessageReceiver as my messageReceiver in service.xml. This combination works perfectly.
> I want to use custom messageReceiver, which is extending org.apache.axis2.rpc.receivers.RPCMessageReceiver. 
> Currently I am just logging some message inside invokeBusinessLogic and invoking super invokeBusinessLogic method.
> During deployment it doen't give any error, but when I tries to access wsdl for it, gives 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>
> Any one knows what wrong happening or what are the steps to implement custom messageReceiver.
> I tried it on tomcat-5.5.20 also, but its giving same issue

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org