We have a field that at times needs to be non-editable but displayed and other times editable independent of user role.
To accomplish that we use a <logic:equals> tag to determine which to display the active inputs or the read-only display with hidden inputs. If we're displaying read-only, then we carry the actual values in a <html:hidden> tag and disable the corresponding <input> tag (e.g., checkbox)... ----- Original Message ----- From: "Jarnot Voytek Contr AU HQ/SC" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Tuesday, January 21, 2003 4:21 PM Subject: RE: Making a Form non-editable > I put the form submit button in that tag, they can see everything else. > > -- > Voytek Jarnot > Quidquid latine dictum sit, altum viditur. > > > -----Original Message----- > From: Curtney Jacobs [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 21, 2003 7:06 AM > To: Struts Users Mailing List > Subject: Re: Making a Form non-editable > > > Hello, > > Acutally, the user can read (see) the data, however, they cannot modify the > data. What you are presenting actually prevents the user from seeing the > data > at all. > > Correct me if I am wrong. > > _CJ > > > On Tuesday 21 January 2003 8:30 pm, Jarnot Voytek Contr AU HQ/SC wrote: > > 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. > > -- > U-Interface.com > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
