You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Paul Spencer <pa...@apache.org> on 2007/02/07 15:17:44 UTC
Attributes enabledOnUserRole and visibleOnUserRole being deprecated?
Per the comment "the attributes enabledOnUserRole and visibleOnUserRole
will be deprecated and replaced by rendered='#{securityContext..}'" on
TOMAHAWK-885[1], I am not sure I like this. Granted securityContext
provides a lot more control, but the attributes are easier to use and
document for the simple stuff.
Why are the attributes being deprecated?
When are the attribute scheduled to be deprecated?
Should their be an Jira issue for the deprecation?
If you would prefer to continue this discussion after the release of
MyFaces 1.1.5, I have no objections.
Paul Spencer
[1]https://issues.apache.org/jira/browse/TOMAHAWK-885
Re: Attributes enabledOnUserRole and visibleOnUserRole being deprecated?
Posted by Mike Kienenberger <mk...@gmail.com>.
Paul,
Performing those tasks would be helpful. Thanks!
On 2/8/07, Paul Spencer <pa...@apache.org> wrote:
> Mike,
> I found the thread title s:secure around 16-aug-2006 [1]. I also found
> the wiki documentation [2].
>
> 1) The wiki page should be move into Tomahawk's documentation. I will
> create a JIRA if you like.
>
> 2) Deprecation of the attributes enabledOnUserRole and visibleOnUserRole
> need to be documented. This includes the TLDs, a "Deprecation" section
> on Tomahawk's website, and the release notes. I will create a JIRA if
> you like.
>
> 3) I will close TOMAHAWK-885 as wontfix with an explanation.
>
> Paul Spencer
>
> [1] http://www.mail-archive.com/dev@myfaces.apache.org/msg16445.html
> [2] http://wiki.apache.org/myfaces/SecurityContext
>
> Mike Kienenberger wrote:
> > Because attributes have to be documented and maintained for every
> > component. They also don't work for non-Tomahawk components.
> >
> > A securityContext approach is more flexible, maintainable, and
> > all-encompassing. We had a long discussion on this a long time ago
> > on the dev list. You could probably find it in the archives.
> >
> > On 2/7/07, Paul Spencer <pa...@apache.org> wrote:
> >> Per the comment "the attributes enabledOnUserRole and visibleOnUserRole
> >> will be deprecated and replaced by rendered='#{securityContext..}'" on
> >> TOMAHAWK-885[1], I am not sure I like this. Granted securityContext
> >> provides a lot more control, but the attributes are easier to use and
> >> document for the simple stuff.
> >>
> >> Why are the attributes being deprecated?
> >>
> >> When are the attribute scheduled to be deprecated?
> >>
> >> Should their be an Jira issue for the deprecation?
> >>
> >> If you would prefer to continue this discussion after the release of
> >> MyFaces 1.1.5, I have no objections.
> >>
> >>
> >> Paul Spencer
> >>
> >> [1]https://issues.apache.org/jira/browse/TOMAHAWK-885
> >>
> >>
> >
>
>
Re: Attributes enabledOnUserRole and visibleOnUserRole being deprecated?
Posted by Paul Spencer <pa...@apache.org>.
Mike,
I found the thread title s:secure around 16-aug-2006 [1]. I also found
the wiki documentation [2].
1) The wiki page should be move into Tomahawk's documentation. I will
create a JIRA if you like.
2) Deprecation of the attributes enabledOnUserRole and visibleOnUserRole
need to be documented. This includes the TLDs, a "Deprecation" section
on Tomahawk's website, and the release notes. I will create a JIRA if
you like.
3) I will close TOMAHAWK-885 as wontfix with an explanation.
Paul Spencer
[1] http://www.mail-archive.com/dev@myfaces.apache.org/msg16445.html
[2] http://wiki.apache.org/myfaces/SecurityContext
Mike Kienenberger wrote:
> Because attributes have to be documented and maintained for every
> component. They also don't work for non-Tomahawk components.
>
> A securityContext approach is more flexible, maintainable, and
> all-encompassing. We had a long discussion on this a long time ago
> on the dev list. You could probably find it in the archives.
>
> On 2/7/07, Paul Spencer <pa...@apache.org> wrote:
>> Per the comment "the attributes enabledOnUserRole and visibleOnUserRole
>> will be deprecated and replaced by rendered='#{securityContext..}'" on
>> TOMAHAWK-885[1], I am not sure I like this. Granted securityContext
>> provides a lot more control, but the attributes are easier to use and
>> document for the simple stuff.
>>
>> Why are the attributes being deprecated?
>>
>> When are the attribute scheduled to be deprecated?
>>
>> Should their be an Jira issue for the deprecation?
>>
>> If you would prefer to continue this discussion after the release of
>> MyFaces 1.1.5, I have no objections.
>>
>>
>> Paul Spencer
>>
>> [1]https://issues.apache.org/jira/browse/TOMAHAWK-885
>>
>>
>
Re: Attributes enabledOnUserRole and visibleOnUserRole being deprecated?
Posted by Mike Kienenberger <mk...@gmail.com>.
Because attributes have to be documented and maintained for every
component. They also don't work for non-Tomahawk components.
A securityContext approach is more flexible, maintainable, and
all-encompassing. We had a long discussion on this a long time ago
on the dev list. You could probably find it in the archives.
On 2/7/07, Paul Spencer <pa...@apache.org> wrote:
> Per the comment "the attributes enabledOnUserRole and visibleOnUserRole
> will be deprecated and replaced by rendered='#{securityContext..}'" on
> TOMAHAWK-885[1], I am not sure I like this. Granted securityContext
> provides a lot more control, but the attributes are easier to use and
> document for the simple stuff.
>
> Why are the attributes being deprecated?
>
> When are the attribute scheduled to be deprecated?
>
> Should their be an Jira issue for the deprecation?
>
> If you would prefer to continue this discussion after the release of
> MyFaces 1.1.5, I have no objections.
>
>
> Paul Spencer
>
> [1]https://issues.apache.org/jira/browse/TOMAHAWK-885
>
>