Return-Path: Delivered-To: apmail-shiro-dev-archive@www.apache.org Received: (qmail 49219 invoked from network); 19 Oct 2010 21:21:13 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Oct 2010 21:21:13 -0000 Received: (qmail 81277 invoked by uid 500); 19 Oct 2010 21:21:13 -0000 Delivered-To: apmail-shiro-dev-archive@shiro.apache.org Received: (qmail 81255 invoked by uid 500); 19 Oct 2010 21:21:13 -0000 Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shiro.apache.org Delivered-To: mailing list dev@shiro.apache.org Received: (qmail 81247 invoked by uid 99); 19 Oct 2010 21:21:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 21:21:13 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 21:21:06 +0000 Received: from jim.nabble.com ([192.168.236.80]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1P8Jbw-0003TH-NR for dev@shiro.apache.org; Tue, 19 Oct 2010 14:20:44 -0700 Date: Tue, 19 Oct 2010 14:20:44 -0700 (PDT) From: Mike K To: dev@shiro.apache.org Message-ID: <1287523244698-5652673.post@n2.nabble.com> In-Reply-To: References: Subject: Re: Proposed changes to Shiro annotations MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I realize I am quite late to this discussion, but I wanted to put my 2 cents in. I am currently using Shrio with AOP, however, I am not using Shiro annotations, instead, using my own AspectJ scheme with point cuts based on jax-rs annotation. One annotation that I have created for myself was @RequiresPermission("domain:action") that can annotate both methods and parameters. In the case of method annotation, the permission is checked. In the case a parameter is annotated the the parameter is converted to string (or a comma separated list if its a collection) and is used as the target in the permission. Mike. -- View this message in context: http://shiro-developer.582600.n2.nabble.com/Proposed-changes-to-Shiro-annotations-tp5223639p5652673.html Sent from the Shiro Developer mailing list archive at Nabble.com.