Hi,
So Obvious solution might be to define proper name spaces for each policy
definition, thus we can minimize the conflict WDYT? and how quickly we can
adopt this enchantments for the future releases, because its seem like we
may required a proper solution and it has to go through RM (may be in IS
space may be in CARBON 5 space)
cheers
Dushan
On Fri, May 10, 2013 at 4:16 PM, Ravi Undupitiya <r...@wso2.com> wrote:
> Hi,
>
>
> The proposed hack for to fix this issue is to parse out the Security
> Scenario wsuid ("WSO2ServiceThrottlingPolicy",
> "RMPolicy", WSO2CachingPolicy"). And to check if one of these exist, and if
> they do, not to disableREST.
>
> But what if the user has asked for a particular service to have
> disableREST set to true, each time the service restarts and the service has
> either throttling, RM or caching, the opposite will now happen: disableREST
> will be set to false.
>
> IMHO, this is not a good solution.
>
>
>
> Thanks,
> Ravi
>
>
> On Fri, May 10, 2013 at 11:20 AM, Asela Pathberiya <as...@wso2.com> wrote:
>
>> 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 <r...@wso2.com> wrote:
>>
>>> Copying below mail to dev.
>>>
>>>
>>> On Thu, May 9, 2013 at 2:17 PM, Ravi Undupitiya <r...@wso2.com> 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: r...@wso2.com
>>> **M: **+94 772 930 712*
>>> *
>>> *Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Asela
>>
>> Mobile : +94 777 625 933
>>
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>
--
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*Member of Integration MC*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
