You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "manthos (JIRA)" <ji...@apache.org> on 2010/12/09 20:54:01 UTC

[jira] Updated: (SHIRO-222) Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean [patch included]

     [ https://issues.apache.org/jira/browse/SHIRO-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

manthos updated SHIRO-222:
--------------------------

    Summary: Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean [patch included]  (was: Register LifecycleBeanPostProcessor before ShiroFilterFactoryBean )

> 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
>         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.
-
You can reply to this email to add a comment to the issue online.