Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Tue, 28 Feb 2012 17:17:46 +0000 (UTC)
From: "Roman Yaroslavtsev (Commented) (JIRA)" <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: 
 <740299319.28761.1330449466571.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <3017489.44411291924203545.JavaMail.jira@thor>
Subject: [jira] [Commented] (SHIRO-222) Register LifecycleBeanPostProcessor
 before ShiroFilterFactoryBean [patch included]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SHIRO-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218360#comment-13218360 ] 

Roman Yaroslavtsev commented on SHIRO-222:
------------------------------------------

Sorry, my suggestion to use Ordered interface was completely incorrect. The simplest solution is to declare LifecycleBeanPostProcessor method as static, to avoid early Configuration bean creation.
                
> Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean [patch included]
> ----------------------------------------------------------------------------------
>
>                 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
>             Fix For: 1.2.0
>
>         Attachments: LifecycleBeanPostProcessor.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira