Adam,
EL doesn't allow arguments in which case isUserInRole() checking
requires the developer to create a managed bean first to then provide
boolean return values. Though not reflected in the JSF spec, I think
that providing out-of-the box security always is a benefit. At least
this way you can ensure it is implemented the est way possible. However,
this goes beyond implementing security on a single UI Component only but
requires security to be enabled on the JSF engine.
Just my 2 cents on it
Frank
Adam Winer wrote:
There has not been a decision on adding either role checking
or force ID to Trinidad.
My personal starting position is that I'd be -1 on adding
either. Role checking is better accomplished via setting
EL on disabled and readOnly, and force ID is unnecessary
in JSF 1.2 with h:form prependId="false" (and the
removal of requirements for using f:subview).
-- Adam
On 8/7/06, Baker,Jonathan <[EMAIL PROTECTED]> wrote:
I believe that I read somewhere that while in incubation the important
attributes of tomahawk (forceid, role checking) would be added to the
trinidad components. Unfortunately I cannot remember or find where I
read that statement. I wanted to verify with the list that this is
true. Will trinidad and tomahawk eventually be merged into one set of
components that support the skinning and things of ADF, but also support
the forceid, and role checking of tomahawk.
JB
--
________________________________
Frank Nimphius
Principal Product Manager
Application Development Tools
Oracle Corporation
mail: [EMAIL PROTECTED]
phone:+49 2058 782481
