Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 73226 invoked from network); 29 Nov 2010 19:07:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Nov 2010 19:07:01 -0000 Received: (qmail 88189 invoked by uid 500); 29 Nov 2010 19:06:53 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 88168 invoked by uid 500); 29 Nov 2010 19:06:53 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 88160 invoked by uid 99); 29 Nov 2010 19:06:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Nov 2010 19:06:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of davelnewton@gmail.com designates 209.85.215.176 as permitted sender) Received: from [209.85.215.176] (HELO mail-ey0-f176.google.com) (209.85.215.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Nov 2010 19:06:48 +0000 Received: by eyz10 with SMTP id 10so2302909eyz.35 for ; Mon, 29 Nov 2010 11:06:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=vnc2vg28BZqr6Rx4zP+XkRh3ejiNwdoVJbG6dmx9VqU=; b=hjvX1Iw0RbI3rzxDirGnnvkVwjLlRzrUUMJ7tSY/VtwEpTViCtL0kOf4oheuzqtiAe B+QHg3Jc2a74XQxr5/QhYHb009cHrsW+0o/q60iKYEUb5ShKNpg/l9B8cySKqSoRw+Jo CGuwbQl4CjUBoryoWM7LSFjBgiVXOGdlpuUoM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=DOYjwOkYwBb1fhvMyjWYQ65fgcqRgFYgVgp6FeMmwlEmaxz75IKXmjTN772KzN/tsq jLqtab6MRTcYhXweAIEC0FFpuFRkP7ob6MykTmH9o+c21GeNS9tKCzwL0XVj3YTTcs64 lWKELYCpjmVMzyCajE8weedXDl74ihClFEyLc= MIME-Version: 1.0 Received: by 10.213.3.16 with SMTP id 16mr499433ebl.79.1291057586406; Mon, 29 Nov 2010 11:06:26 -0800 (PST) Received: by 10.213.14.20 with HTTP; Mon, 29 Nov 2010 11:06:25 -0800 (PST) In-Reply-To: References: Date: Mon, 29 Nov 2010 14:06:25 -0500 Message-ID: Subject: Re: Link Display Logic From: Dave Newton To: Struts Users Mailing List Content-Type: multipart/alternative; boundary=0015174c3f4ad287d7049635c4ff --0015174c3f4ad287d7049635c4ff Content-Type: text/plain; charset=ISO-8859-1 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 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" > --0015174c3f4ad287d7049635c4ff--