Return-Path: Delivered-To: apmail-shiro-dev-archive@www.apache.org Received: (qmail 12263 invoked from network); 9 Dec 2010 19:50:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Dec 2010 19:50:28 -0000 Received: (qmail 89883 invoked by uid 500); 9 Dec 2010 19:50:28 -0000 Delivered-To: apmail-shiro-dev-archive@shiro.apache.org Received: (qmail 89867 invoked by uid 500); 9 Dec 2010 19:50:28 -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 89859 invoked by uid 99); 9 Dec 2010 19:50:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 19:50:28 +0000 X-ASF-Spam-Status: No, hits=-1998.7 required=10.0 tests=ALL_TRUSTED,URI_HEX X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 19:50:25 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB9Jo3rT022922 for ; Thu, 9 Dec 2010 19:50:03 GMT Message-ID: <3017489.44411291924203545.JavaMail.jira@thor> Date: Thu, 9 Dec 2010 14:50:03 -0500 (EST) From: "manthos (JIRA)" To: dev@shiro.apache.org Subject: [jira] Created: (SHIRO-222) Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean ------------------------------------------------------------------ Key: SHIRO-222 URL: https://issues.apache.org/jira/browse/SHIRO-222 Project: Shiro Issue Type: Bug Components: Integration: Spring Affects Versions: 1.1.0 Reporter: manthos LifecycleBeanPostProcessor needs to be registred before ShiroFilterFactoryBean because... ShiroFilterFactoryBean itself is a BeanPostProcessor, like LifecycleBeanPostProcessor too. So during AbstractApplicationContext.registerBeanPostProcessors() these two beans are created and added to nonOrderedPostProcessors, after then they get registered. At this execution point ShiroFilterFactoryBean is already created with its SecurityManager and defined Realms. So LifecycleBeanPostProcessor will not effect anymore on Realms init. http://shiro-user.582556.n2.nabble.com/Shiro-and-Spring-with-ShiroFilterFactoryBean-td5811127.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.