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 On Thu, Jan 29, 2009 at 1:24 AM, Ugo <[email protected]> wrote: > > Nandana, > > I actually did not use the web console to modify and apply the echo service > policy. I only modified the file scenario17-policy.xml before starting > WSAS, > thinking that the modified policy would be picked up at initialization > time. > But it looks like you are telling me that it does not work that way. > > So I put back the original scenario17-policy.xml and I started WSAS again. > In the console, I went into the "Edit Service Policies" option for the echo > service. There I tried to remove the following code: > > <sp:EncryptedParts > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> > <sp:Body /> > </sp:EncryptedParts> > > But when I click "Update", I get message "Unable to update binding policy". > > Thank you, > Ugo > -- > View this message in context: > http://www.nabble.com/Problem-turning-encryption-off-in-sts-sample-tp21628022p21713451.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 > -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
_______________________________________________ Wsas-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/wsas-java-user
