Issue Type: Feature Request Feature Request
Affects Versions: 1.3.1
Assignee: Unassigned
Components: authorization
Created: 17/Feb/14 8:01 AM
Description:

It is not clear how @Secure annation should behave. There are following scenarios, which should be documented so user avoids bad usage of annotation:

1/ Precedence when used in class and its parent
2/ Precedence when used in class and its method
3/ Usage on interfaces. Is it possible? Is implementation able to override definition on interface?
Project: AeroGear Security
Priority: Major Major
Reporter: Karel Piwko
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