[
https://issues.apache.org/jira/browse/SHIRO-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766882#comment-13766882
]
Les Hazlewood commented on SHIRO-345:
-------------------------------------
Hi Diallo,
I totally agree - we should be doing this in the newer Spring AOP way. Could
you please submit that Maven project? I think it will help us produce a
solution faster.
Thanks!
> Annotations support of shiro is not compatible to aop enabled spring mvc
> controllers.
> -------------------------------------------------------------------------------------
>
> Key: SHIRO-345
> URL: https://issues.apache.org/jira/browse/SHIRO-345
> Project: Shiro
> Issue Type: Bug
> Components: Authorization (access control)
> Affects Versions: 1.2.0
> Reporter: DIALLO Mamadou BObo
> Labels: aop, authorization, spring
> Original Estimate: 4m
> Remaining Estimate: 4m
>
> Seems like the way we actualy integrate shiro to work with spring is not
> compatible with spring's own aop stack. I've verified this issue at least on
> spring's @Controller beans.
> This seems to be due to the fact that we proxy the classes marked with
> shiro's annotations.
> To reproduce this issue:
> 1. Create a spring beans that is annotated with either @Component or
> @Controller.
> 2. Add shiro security annotations to this class.
> 3. then configure the shiro annotations as advised here:
> http://shiro.apache.org/spring.html
> I can extract a sample maven project that reproduce this issue.
> I think that we should add annotations support to spring enabled web app the
> same way all others spring components does, through spring's own AOP stack.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
