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

Davanum Srinivas updated AXIS2-1748:
------------------------------------

    Assignee: Deepal Jayasinghe

> It don't work to provide a wsdl inside the aar when deploying the war 
> unexploded in WebLogic
> --------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1748
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1748
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.1
>         Environment: Windows XP
> Bea WebLogic 9.2
>            Reporter: Erland Isaksson
>         Assigned To: Deepal Jayasinghe
>         Attachments: DeveloperService.wsdl, services.xml
>
>
> 1. I build a aar with an included wsdl 
> 2. I include the built aar package in a war (the same contents as axis2.war 
> but renamed to DeveloperServerAxis.war)
> 3. I deploy the war in WebLogc (its not delpoyed exploded)
> The result is that when I access the webservice as:
> http://localhost:7001/DeveloperServerAxis/services/DeveloperService?wsdl
> I just get the error:
> 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).
> If I deploy the same war explored everything works correct and the wsdl is 
> shown when accessing the web service with ?wsdl

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to