shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SHIRO-185) Shiro Annotations in Spring apps: annotations on method implementations not handled when using Spring's DefaultAutoProxyCreator
Date Sun, 18 Jul 2010 09:27:49 GMT

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

Les Hazlewood resolved SHIRO-185.
---------------------------------

    Resolution: Fixed

Fix committed to trunk with tests for two different types of Spring AOP configuration.

> Shiro Annotations in Spring apps:  annotations on method implementations not handled
when using Spring's DefaultAutoProxyCreator
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-185
>                 URL: https://issues.apache.org/jira/browse/SHIRO-185
>             Project: Shiro
>          Issue Type: Bug
>          Components: Integration: Spring
>    Affects Versions: 1.0.0
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> When using Spring's DefaultAutoProxyCreator mechanism to enable Shiro security checks
via annotations (@RequiresAuthentication, @RequiresPermissions, etc), Shiro annotations on
Interface methods are the only ones that are processed successfully.  If a method implementatin
is annotated directly,  the authorization interceptor is never triggered during a method call.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message