I tried with WSAS 2.3 and was able to reproduce following your steps. It seems a bug and I will raise a JIRA. The trunk is drastically changed for WSAS 3.0 and now the policy editing support is a lot improved. Will it be option for you to use WSAS 3.0 ?
thanks, Nandana On Tue, Feb 3, 2009 at 8:27 AM, Ugo <[email protected]> wrote: > > Hi Nandana, > > Were you able to reproduce the problem I encountered? > > Thank you, > Ugo > > > Hi Ugo, > Normally you cannot update the policy when it is invalid. For example, if > you have undeclared namespace prrfix, such things occur. But if you only > deleted the encrypted parts assertions, it can't be the case. Anyway I will > try the scenario and let you know. > > thanks, > nandana > > -- > View this message in context: > http://www.nabble.com/Problem-turning-encryption-off-in-sts-sample-tp21628022p21803092.html > Sent from the WSO2 WSAS Users mailing list archive at Nabble.com. > > > _______________________________________________ > Wsas-java-user mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/wsas-java-user >
_______________________________________________ Wsas-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/wsas-java-user
