Cwikius-Spring
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SEC-1888: Improving the doc on (not) using multiple annotation types in the same class.

This commit is contained in:
Luke Taylor 2012-01-31 18:56:17 +00:00
parent f97463cdb5
commit b493afa18c
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/manual/src/docbook/namespace-config.xml
View File

@ -880,14 +880,20 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
}
</programlisting>Expression-based
annotations are a good choice if you need to define simple rules that go beyond
checking the role names against the user's list of authorities. You can enable more
than one type of annotation in the same application, but you should avoid mixing
annotations types in the same interface or class to avoid confusion. <note>
checking the role names against the user's list of authorities. <note>
<para>The annotated methods will only be secured for instances which are defined as
Spring beans (in the same application context in which method-security is
enabled). If you want to secure instances which are not created by Spring (using
the <literal>new</literal> operator, for example) then you need to use AspectJ.
</para>
</note>
<note>
<para>
You can enable more than one type of annotation in the same application, but
only one type should be used for any interface or class as the behaviour will not
be well-defined otherwise. If two annotations are found which apply to a particular
method, then only one of them will be applied.
</para>
</note> </para>
<section xml:id="ns-protect-pointcut">
<title>Adding Security Pointcuts using <literal>protect-pointcut</literal></title>
@ -904,7 +910,9 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
whose class names end in "Service". Only users with the
<literal>ROLE_USER</literal> role will be able to invoke these methods. As with
URL matching, the most specific matches must come first in the list of
pointcuts, as the first matching expression will be used. </para>
pointcuts, as the first matching expression will be used. Security
annotations take precedence over pointcuts.
</para>
</section>
</section>
</section>