[wsas-java-dev] [jira] Closed: (WSAS-346) Errorneous messages in WSDL1.1, WSDL2, Policy, Schema views when the service is inactive

[Charitha Kankanamge (JIRA)]

     [ http://www.wso2.org/jira/browse/WSAS-346?page=all ]

Charitha Kankanamge closed WSAS-346.
------------------------------------


Verified in WSAS-2.1-RC4 and closed the bug.

> Errorneous messages in WSDL1.1, WSDL2, Policy, Schema views when the service is inactive
> ----------------------------------------------------------------------------------------
>
>                 Key: WSAS-346
>                 URL: http://www.wso2.org/jira/browse/WSAS-346
>             Project: WSO2 WSAS
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: Nightly
>         Environment: WinXP, JDK 1.5, IE6.0.0.29
>            Reporter: Yumani Ranaweera
>         Assigned To: Saminda Wishwajith Abeyruwan 
>            Priority: Minor
>             Fix For: 2.0-RC2
>
>
> Steps to recreate
> -----------------------
> 1. Login to admin console
> 2. Go to Services>Service Management page of a service and deactivate the service.
> 3. Click on WSDL 1.1 link --------> In addition to the text "Service echo is inactive. Cannot display WSDL document.", it also displays "echo" in a later line.
> 4. Click on WSDL 2.0 link --------> In addition to the text  "Service echo is inactive. Cannot display WSDL document." it also displays text given below;
> echo This endpoint exposes a SOAP 11 binding over a HTTPSThis endpoint exposes a SOAP 12 binding over a HTTPSThis endpoint exposes a HTTP binding over a HTTPSThis endpoint exposes a SOAP 11 binding over a HTTPThis endpoint exposes a SOAP 12 binding over a HTTPThis endpoint exposes a HTTP binding over a HTTP
> 5. Click on Schema link --------> In addition to the text "Service echo is inactive. Cannot display Schema." it display the infomation shown below;
> Schemas for echo service
> Schema 0
> Schema 1
> 6. Click on Policy link ---------> In addition to the text "Service echo is inactive. Cannot display policies.", it also displays below;
> Policy not found!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira