Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 20964 invoked from network); 7 Feb 2007 20:31:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2007 20:31:19 -0000 Received: (qmail 98456 invoked by uid 500); 7 Feb 2007 20:31:24 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 98394 invoked by uid 500); 7 Feb 2007 20:31:24 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 98383 invoked by uid 99); 7 Feb 2007 20:31:24 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 12:31:24 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mkienenb@gmail.com designates 64.233.162.237 as permitted sender) Received: from [64.233.162.237] (HELO nz-out-0506.google.com) (64.233.162.237) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 12:31:14 -0800 Received: by nz-out-0506.google.com with SMTP id n29so143277nzf for ; Wed, 07 Feb 2007 12:30:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KSwsVgZ7oVPnbVHQsrwIhzg2pVQPecE3Nf9pO1jxe9capAw7758IZ0G/LSdufSU/i1ygpDNfp6IvzzuAasy2w8qp5lg4YXtTeaHbobDH7fHf6pz7k/2CXoYaHii6e3M8IVN3j/vTF7DWh3G+p3c7PZD75dgpA/7BYPn9ZvkBWQs= Received: by 10.114.12.9 with SMTP id 9mr2386525wal.1170880253841; Wed, 07 Feb 2007 12:30:53 -0800 (PST) Received: by 10.114.160.3 with HTTP; Wed, 7 Feb 2007 12:30:53 -0800 (PST) Message-ID: <8f985b960702071230x25bbc034t21890c5a07439585@mail.gmail.com> Date: Wed, 7 Feb 2007 15:30:53 -0500 From: "Mike Kienenberger" To: "MyFaces Development" Subject: Re: Attributes enabledOnUserRole and visibleOnUserRole being deprecated? In-Reply-To: <45C9DF88.8010709@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45C9DF88.8010709@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org 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 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 > >