That is a very interesting tag, I have never used it - thanks Laurie!! Cheers, Alex.
On 7/14/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > > Not sure what a .def file is, but I think you're on the right track with > combining them and using conditional logic within the JSP to control > what's > displayed based on user role. Look at <logic:present role=''/> for a > simple > way to wrap role-dependent markup in your JSPs: > > http://struts.apache.org/userGuide/struts-logic.html#present > > L. > > Aleksandar Matijaca wrote: > > Hi there, > > > > I have an application that I am working on that requires two different > role > > levels (administrator and user). > > The administrator, will have some extra links visible to them. I want to > use > > only one struts-config file. > > I am currently running into a scalability issue -- here is what I mean: > > > > > > > > <action path="/someAction" ....... > > > > > <forward name="a_success" path="someAdministratorPath.def"> <!-- I am > using > > tiles --> > > <forward name="u_success" path="someUserPath.def"> <!-- I am using tiles > --> > > > > </aciton> > > > > The someAdministratorPath.def has a jsp with different kind of a menu > > structure - for administrators only, > > and someUserPath.def has a jsp with a subset of different menu > structures -- > > the only real difference between > > the two .def files is a single jsp. > > > > Somehow the above seems awkward and unscalable to me, and I am afraid I > will > > run into a problem later. > > I know that I can probably put in some <c:if statements in one of the > JSPs, > > and there discriminate between > > a User and Administrator, but somehow, that seems like a band-aid > solution. > > > > If you have any idea on how to restructure this thing, please let me > know. > > > > Thanks, Alex. > > > > > -- > Laurie, Open Source advocate, Java geek and novice blogger: > http://www.holoweb.net/~laurie/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
