That's what I do, I wrote a tag as such: <myTags:ifUserInRole value="role1,role2"> markup in here is only visible to those in role1 or role2 </myTags:ifUserInRole>
This breaks the 'presentation only' rule a little bit, but makes for a much more user-friendly UI. -- Voytek Jarnot Quidquid latine dictum sit, altum viditur. -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 2:26 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: Making a Form non-editable On Tue, 21 Jan 2003, Curtney Jacobs wrote: > Date: Tue, 21 Jan 2003 10:15:14 +0000 > From: Curtney Jacobs <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Making a Form non-editable > [SNIP] > Any suggestions or comments are greatly appreciated. > One off-the-wall way to accomplish your goal would be to simply skip generating the submit button if your user has read-only access. Even if the user tries to mess with the individual form values, they can't submit (unless they're willing to hand-type a huge long URL into the location bar of the browser -- but disabling individual fields doesn't prevent that either.) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
