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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/02/15 09:08:06 UTC
[jira] Assigned: (AXIS2-2174) Unable to retrieve the wsdl using
?wsdl when sandesha is enagaged to a service
[ https://issues.apache.org/jira/browse/AXIS2-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2174:
----------------------------------------
Assignee: Deepal Jayasinghe
> Unable to retrieve the wsdl using ?wsdl when sandesha is enagaged to a service
> ------------------------------------------------------------------------------
>
> Key: AXIS2-2174
> URL: https://issues.apache.org/jira/browse/AXIS2-2174
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: modules
> Affects Versions: 1.1.1
> Environment: winxp, jdk1.5, sandesha2 1.1
> Reporter: Charitha Kankanamge
> Assigned To: Deepal Jayasinghe
> Priority: Critical
> Attachments: esbservice.aar
>
>
> I deployed the attached service which was engaged to sandesha2. When I issued the ?wsdl in browser URL, I got the following error.
> Unable to generate WSDL for this service
> 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).
> The wsdl is generated correctly when '<module ref="sandesha2" />' is removed from the services.xml.
--
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