[ 
https://issues.apache.org/jira/browse/AXIS2-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001677#comment-14001677
 ] 

Saurab Rajkarnikar edited comment on AXIS2-5651 at 5/19/14 1:38 PM:
--------------------------------------------------------------------

Attached are my aar package file, and wsdl and xml files.


was (Author: saurjk):
Here are my aar package file, and wsdl and xml files.

> Getting message "Trouble processing wsdl file :null" when deploying wsdl 2.0 
> aar file
> -------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5651
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5651
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.6.2
>         Environment: Windows 7 Professional, Axis2 Binary
>            Reporter: Saurab Rajkarnikar
>              Labels: deploy, newbie, wsdl2.0
>         Attachments: KWSHeader.xsd, services.xml, tmkennunglesenService.aar, 
> tmkennunglesenService.wsdl
>
>
> I have a wsdl skeleton which generates .aar file fine. However, whenever I 
> try to deploy the package I get a "Trouble processing wsdl file :null" which 
> occurs when ((WSDL20ToAllAxisServicesBuilder) 
> axisServiceBuilder).populateAllServices(); command is run in 
> ArchiveReader.java. What seems to be the problem? Is there a problem with my 
> wsdl file or services.xml file? or is it sth else?
> Here is the error message:
> [INFO] Deployoing wsdl 2.0
> [INFO] Trouble processing wsdl file :null
> [INFO] Axus Fault : null
> [INFO] Reason : null
> [INFO] Returning null
> [INFO] Deploying Web service: tmkennunglesenService.aar - 
> file:/C:/Users/Public/Server/axis2-1.6.2/repository/services/tmkennunglesenService.aar
> I added a few log values as a test.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to