[ http://issues.apache.org/jira/browse/AXIS2-1395?page=all ]
Ruwan Linton updated AXIS2-1395:
--------------------------------
Attachment: services.xml
This is the services.xml file which got deployed
> Incorrect services.xml files are getting deployed without errors in axis2
> without generating WSDL file
> ------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1395
> URL: http://issues.apache.org/jira/browse/AXIS2-1395
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1
> Reporter: Ruwan Linton
> Priority: Critical
> Attachments: services.xml
>
>
> I have writen a services.xml(will attach) file for the service class with a
> RPCMessagereceiver specified as the MR in the service level without specifing
> the MEP and specified an operation without specifing neither the MR nor the
> MEP, expecting the operation to take the RPC MR as the MR. But this did not
> work. I found that this behaviour is not allowed in Axis2.
> But the problem is Axis2 deploy this service without giving an error and it
> was shown in the Axis2 webapps service display as a good service. But I
> couldn't access this service and also the WSDL file was not generated. I
> think in this case Axis2 should give an error message without deploying it.
> Showing this service as a deployed working service is worst.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
