Issue may be related to this [1]. Because when you applied caching, RM and throttling policy, there are also persist as security policies (with security policy name space). Therefore security component would see this as security policy and try to process....
[1] https://wso2.org/jira/browse/CARBON-13927 Thanks, Asela On Thu, May 9, 2013 at 5:26 PM, Ravi Undupitiya <[email protected]> wrote: > Copying below mail to dev. > > > On Thu, May 9, 2013 at 2:17 PM, Ravi Undupitiya <[email protected]> wrote: > >> Hello, >> >> I'm looking at ESBJAVA-1845. The problem is described below: >> >> Enabling throttling on a service causes this to be added to the service >> WSDL: >> >> <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; >> xmlns:wsu=" >> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; >> wsu:Id="WSO2ServiceThrottlingPolicy"> >> <wsp:ExactlyOne> >> <wsp:All/> >> </wsp:ExactlyOne> >> </wsp:Policy> >> >> >> This makes the security component call disableRESTCalls and >> applySecurityParameters which turns disableREST to true. This happens every >> time we start the server. >> >> >> What is the best way to handle this case? >> >> >> >> Thanks, >> Ravi >> > > -- > *Ravi Undupitiya* > Software Engineer; WSO2 Inc.; http://wso2.com > * > * > *E-mail: [email protected] > **M: **+94 772 930 712* > * > *Lean . Enterprise . Middleware > -- Thanks & Regards, Asela Mobile : +94 777 625 933
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
