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

Posted to dev@shiro.apache.org by "Francois Papon (Jira)" <ji...@apache.org> on 2021/05/19 12:16:00 UTC

[jira] [Resolved] (SHIRO-804) Avoid conflicts with spring boot aop

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

Francois Papon resolved SHIRO-804.
----------------------------------
    Resolution: Resolved

> Avoid conflicts with spring boot aop
> ------------------------------------
>
>                 Key: SHIRO-804
>                 URL: https://issues.apache.org/jira/browse/SHIRO-804
>             Project: Shiro
>          Issue Type: Improvement
>          Components: Integration: Spring
>    Affects Versions: 1.7.0
>            Reporter: skywalker
>            Assignee: Les Hazlewood
>            Priority: Minor
>             Fix For: 2.0.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> If there is a spring-boot-starter-aop dependency in the project's classpath, Spring will automatically create a bean named "org.springframework.aop.config.internalAutoProxyCreator".
> This will cause Spring beans to be proxied twice. If one is a JDK dynamic proxy and the other is a CGLIB proxy, then the system will fail to start.
> We may be able to avoid such errors by modifying the defaultAdvisorAutoProxyCreator method of the ShiroAnnotationProcessorAutoConfiguration class.
> I have tested this modification in my own project and it works. Sorry, my English is not very good, this paragraph is written using Google Translate



--
This message was sent by Atlassian Jira
(v8.3.4#803005)