On Wed, Mar 2, 2011 at 7:08 PM, Afkham Azeez <[email protected]> wrote:

> Senaka,
> Was this changed?
>

Not committed yet. I will do that after I try out whole thing on a new
build.

Thanks,
Senaka.

>
> Azeez
>
>
> On Wed, Feb 9, 2011 at 3:48 PM, Senaka Fernando <[email protected]> wrote:
>
>> +1.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Feb 9, 2011 at 11:33 AM, Afkham Azeez <[email protected]> wrote:
>>
>>> Here is what I'm talking about.
>>>
>>> *Scenario 1*
>>> <permissions>
>>>    <all>
>>>
>>>
>>> <require-permission>/permission/admin/manage/resources/govern/metadata/add</require-permission>
>>>
>>>  
>>> <require-permission>/permission/admin/manage/resources/browse</require-permission>
>>>    </all>
>>> </permissions>
>>>
>>> *Scenario 2*
>>> <permissions>
>>>    <exactly-one>
>>>
>>>
>>> <require-permission>/permission/admin/manage/resources/govern/metadata/add</require-permission>
>>>
>>>  
>>> <require-permission>/permission/admin/manage/resources/browse</require-permission>
>>>     </exactly-one>
>>> </permissions>
>>>
>>>
>>> On Wed, Feb 9, 2011 at 11:21 AM, Danushka Menikkumbura <
>>> [email protected]> wrote:
>>> > +1.
>>> >
>>> > The impression I got when I saw the sample configuration was having one
>>> or
>>> > more permissions would let you see the menu.
>>> >
>>> > Danushka
>>> >
>>> > On Wed, Feb 9, 2011 at 7:59 AM, Afkham Azeez <[email protected]> wrote:
>>> >>
>>> >> Senaka,  I think a better way of doing this is to have a configuration
>>> >> model simile to ws-policy configuration. You can either require all
>>> >> permissions or at least one
>>> >>
>>> >> -------------------------
>>> >> Sent from my APD
>>> >>
>>> >> On Feb 8, 2011 11:00 PM, "Senaka Fernando" <[email protected]> wrote:
>>> >> > Hi all.
>>> >> >
>>> >> > So far, we've been having menu items which depend only on a single
>>> UI
>>> >> > permission. So, ideally, all the BE functionality that belongs to
>>> the
>>> >> > various components of the JSP page(s) to which the menu points to
>>> need
>>> >> > to be
>>> >> > a derivation of that permission. However, this was a limitation for
>>> [1],
>>> >> > and
>>> >> > with the fix for [1] (r86929), we now can have menu items that
>>> require
>>> >> > more
>>> >> > than one permission.
>>> >> >
>>> >> > Ex:-
>>> >> > <menu>
>>> >> > <id>governance_schema_menu</id>
>>> >> > <i18n-key>governance.schema.menu</i18n-key>
>>> >> >
>>> >> >
>>> >> >
>>> <i18n-bundle>org.wso2.carbon.governance.schema.ui.i18n.Resources</i18n-bundle>
>>> >> > <parent-menu>add_metadata_sub_menu</parent-menu>
>>> >> > <link>../schema/schema.jsp</link>
>>> >> > <region>region3</region>
>>> >> > <order>4</order>
>>> >> > <style-class>manage</style-class>
>>> >> > <icon>../schema/images/schema.gif</icon>
>>> >> >
>>> >> >
>>> >> >
>>> <require-permission>/permission/admin/manage/resources/govern/metadata/add</require-permission>
>>> >> >
>>> >> >
>>> >> >
>>> <require-permission>/permission/admin/manage/resources/browse</require-permission>
>>> >> > </menu>
>>> >> >
>>> >> > The Add --> Schema menu will be displayed only if users can both add
>>> >> > metadata and browse resources on the registry.
>>> >> >
>>> >> > [1] https://wso2.org/jira/browse/CARBON-8311
>>> >> >
>>> >> > Thanks,
>>> >> > Senaka.
>>> >> >
>>> >> > --
>>> >> > *Senaka Fernando*
>>> >> > Product Manager - WSO2 Governance Registry;
>>> >> > Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>>> >> > Member; Apache Software Foundation; http://apache.org
>>> >> >
>>> >> > E-mail: senaka AT wso2.com
>>> >> > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>>> >> >
>>> >> > *Lean . Enterprise . Middleware
>>> >>
>>> >> _______________________________________________
>>> >> Carbon-dev mailing list
>>> >> [email protected]
>>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > Carbon-dev mailing list
>>> > [email protected]
>>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Afkham Azeez
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>>> ,
>>>
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> email: [email protected] cell: +94 77 3320919
>>> blog: http://blog.afkham.org
>>> twitter: http://twitter.com/afkham_azeez
>>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*<http://www.apache.org/>
> *
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2, Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to