[wsas-java-dev] [jira] Resolved: (WSAS-736) Policies cannot be engaged to services via WSAS

Keith Godwin Chapman (JIRA) jira at wso2.org
Sun Apr 6 21:33:18 PDT 2008


     [ https://wso2.org/jira/browse/WSAS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Godwin Chapman resolved WSAS-736.
---------------------------------------

    Resolution: Fixed

Applied patch in revision 15590 to fix the blocking issue for the mashup server.

> Policies cannot be engaged to services via WSAS
> -----------------------------------------------
>
>                 Key: WSAS-736
>                 URL: https://wso2.org/jira/browse/WSAS-736
>             Project: WSO2 WSAS
>          Issue Type: Bug
>            Reporter: Keith Godwin Chapman
>            Assignee: Sanka Samaranayake
>            Priority: Blocker
>         Attachments: WSAS_736.patch
>
>
> Policies cannot be engaged to services via WSAS. 
> In the Mashup Server we use SecurityScenarioConfigAdmin to engage policies to our admin services and as of late (due to changes in axis2) this is not working. Policies engaged are not displayed in the WSDL as well. This is blocking the mashup server as even the login function is broken.

-- 
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

        



More information about the Wsas-java-dev mailing list