[
https://wso2.org/jira/browse/WSAS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-569.
------------------------------------
Resolution: Fixed
The related Axis2 issue has been fixed. Verified in latest WSAS and closed the
bug
> The generated WSDL2 does not have soap11, http binding if the wsdl is
> included in service archive
> -------------------------------------------------------------------------------------------------
>
> Key: WSAS-569
> URL: https://wso2.org/jira/browse/WSAS-569
> Project: WSO2 WSAS
> Issue Type: Bug
> Components: core
> Environment: winxp, jdk15, WSAS-2.1-RC4
> Reporter: Charitha Kankanamge
> Assignee: Saminda Wishwajith Abeyruwan
> Attachments: charithacal.aar
>
>
> The generated wsdl2 (?wsdl2) does not have soap11 and http bindings if a wsdl
> is included in the service archive.
> Steps to reproduce:
> ================
> 1. Deploy the attached service archive (Which includes a wsdl)
> 2. Go to service and service group management page
> 3. Click on the wsdl2 link of the deployed service
> Check "wsdl2:binding" elements. You will see only the Soap12 binding there.
> Now remove the wsdl from the service archive. Soap11 and http bindings will
> be added to the wsdl2 document.
> *Since this is an axis2 issue, I'll report this in Axis2 JIRA as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
