This annotation is used within the
represent the security constraints to be applied to all HTTP protocol
methods for which a corresponding
NOT occur within the
The default authorization semantic.
This value is insignificant when
non-empty array, and should not be specified when a non-empty
array is specified for rolesAllowed.
EmptyRoleSemantic to be applied when
rolesAllowed returns an empty (that is, zero-length) array.
The data protection requirements (i.e., whether or not SSL/TLS is
required) that must be satisfied by the connections on which requests
indicating the data protection that must be provided by the connection.
The names of the authorized roles.
Duplicate role names appearing in rolesAllowed are insignificant and
may be discarded during runtime processing of the annotation. The String
has no special meaning as a role name (should it occur in
- an array of zero or more role names. When the array contains
zero elements, its meaning depends on the
returned by the
value method. If
rolesAllowed returns a zero length array,
access is to be denied independent of authentication state and identity.
indicates that access is to be allowed independent of authentication
state and identity. When the array contains the names of one or more
roles, it indicates that access is contingent on membership in at
least one of the named roles (independent of the
EmptyRoleSemantic returned by the