Hi Anjana, I don't think there is an issue with removing the security policies in AS 5.2.1. You can verify this by looking at the service WSDL. The issue you are reporting related to transports is not an issue rather it's a feature.
When users enable a security policy like UT, we remove the all the transports (http, jms, local etc.) except https from the service. When the user disables security, we do not go and try to re-enable all the existing transports since we do not know which transports the user needs/has used before. What if the user has exposed the service only via https even before applying security? It would be wrong if we enable other transports automatically. Therefore, the user has to consciously re-enable the transports he needs. Regards, KasunG On Fri, Mar 14, 2014 at 6:15 PM, Anjana Fernando <[email protected]> wrote: > Hi, > > I created an issue for $subject here [1], can someone from AS please look > into this. > > [1] https://wso2.org/jira/browse/WSAS-1686 > > Cheers, > Anjana. > -- > *Anjana Fernando* > Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* <http://kasunbg.org> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
