David M. Karr wrote:
"Ted" == Ted Husted <[EMAIL PROTECTED]> writes:
Ted> There's a request tag in Jakarta taglibs that supports isUserInRole (among other things), so I would suggest
Ted> that we go with three and refer people to taglibs for the missing functionality (still all in the family :0)
Ted> The role functionality is new in 1.1, and so people going from 1.0 to struts-el won't even miss it.
I use <logic:present role="administrator"> in several places in a 1.0
app that uses container managed security. So...I for one would miss it
a little.
Just so it's clear, I assume you're referring to a taglib in the Jakarta
taglibs project, and NOT the JSTL.
I'm a little hesitant to force some people using Struts-EL to include still
another taglib in their set of taglibs. Not to mention one that is a little
(just a little) further away from the mainstream than Struts and the JSTL.
There will be a set of people upgrading from 1.0.2 to 1.1 who won't miss it,
but beta versions of 1.1 have been stable for such a long time, I think the
number of 1.1 users is larger than might be expected for a beta release.
My only argument against creating "logic-el:present" is "cleanliness", as all
but one of the features of "logic:present" are available in the JSTL (not to
mention that attaching "role-checking" features to "logic:present" just seems
odd). However, when I look at it from a pragmatic viewpoint, I realize that's
less important than simple convenience.
If it helps make it seem "cleaner", don't look at it as "role-checking",
look at it as "attribute value checking" -- now that's logic ;-)
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
