Yes. That is what we do.
It is a bit if a balancing act but if the whole form becomes readonly then
we have a readonly version with just bean write tags.
The Tiles library helps out alot here.
As for level switching, we use logic equals that looks at a boolean field
set by the loading action.
I also found that the pages may load quicker with out so many tags.
Curtney Jacobs <[EMAIL PROTECTED]> on 01/21/2003 07:16:09 AM
Please respond to "Struts Users Mailing List"
<[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
cc:
Subject: Re: Making a Form non-editable
To everyone,
would it better to just have a seperate view to display read only data. In
other words, do not use the form to display the queried data. But, simply
use a JSP page to display the data (naturally, with proper formatting).
The above seems a tad bit cumbersome or redundant; having two seperate
views
for the display of the same data, however for different purposes.
Comments???
_CJ
On Tuesday 21 January 2003 1:05 pm, Curtney Jacobs wrote:
> 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]>
