Dave, Utilizing your suggestion, it sounds like it would be possible to utilize the s:action tag? I guess, what would your custom tag do?
It sounds like, either way, you'd need to call the action from your jsp/view to return a jsp fragment with either the authorized links or nothing. Am I understanding that correctly? Beez -----Original Message----- From: Dave Newton [mailto:davelnew...@gmail.com] Sent: Monday, November 29, 2010 2:06 PM To: Struts Users Mailing List Subject: Re: Link Display Logic I'll generally expose permission info through an action (or whatever model makes it to the page) and use a custom tag to really clarify and narrow the purpose of that particular JSP/etc. logic. Other than that, though, not sure what else I'd really do, if I'm trying to stay within the S2 framework. Spring Security is another option. Dave On Mon, Nov 29, 2010 at 1:41 PM, Biesbrock, Kevin <biesbrock.ke...@aoins.com > wrote: > Hello users. I'm Kevin, first time caller, long time listener (Mr. > Obvious reference). > > I have two reports and need to display a link for each if the > following conditions are met: > 1. The user is authorized to view the reports (they are secured), > and > 2. The specific report currently exists > > Both of these conditions are determined via predefined methods (they > are "black boxes" to me). > > Following the MVC pattern, what is the best way to split up the > display logic of this such that my links are displaying to the > appropriate users when they exist? > > The links will display on the home page. So I thought about > determining these factors in the home action and wrapping s:if tags > around links to the reports. It seems simple enough, I was just > curious if there was a different and/or better approach. > ____ > Thank you for your time, > Kevin - "Beez" > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
