org.jboss.resteasy.plugins.interceptors

Class RoleBasedSecurityFilter

java.lang.Object

org.jboss.resteasy.plugins.interceptors.RoleBasedSecurityFilter

All Implemented Interfaces:

ContainerRequestFilter

public class RoleBasedSecurityFilter
extends Object
implements ContainerRequestFilter

Version:

$Revision: 1 $

Author:

Bill Burke

Field Summary

Fields

Modifier and Type	Field and Description
protected boolean	denyAll
protected boolean	permitAll
protected String[]	rolesAllowed

Constructor Summary

Constructors

Constructor and Description
RoleBasedSecurityFilter(String[] rolesAllowed, boolean denyAll, boolean permitAll)

Method Summary

Methods

Modifier and Type	Method and Description
void	filter(ContainerRequestContext requestContext) Filter method called before a request has been dispatched to a resource.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

rolesAllowed

protected String[] rolesAllowed

denyAll

protected boolean denyAll

permitAll

protected boolean permitAll

Constructor Detail

RoleBasedSecurityFilter

public RoleBasedSecurityFilter(String[] rolesAllowed,
                       boolean denyAll,
                       boolean permitAll)

Method Detail

filter

public void filter(ContainerRequestContext requestContext)
            throws IOException

Description copied from interface: ContainerRequestFilter

Filter method called before a request has been dispatched to a resource.

Filters in the filter chain are ordered according to their javax.annotation.Priority class-level annotation value. If a request filter produces a response by calling ContainerRequestContext.abortWith(javax.ws.rs.core.Response) method, the execution of the (either pre-match or post-match) request filter chain is stopped and the response is passed to the corresponding response filter chain (either pre-match or post-match). For example, a pre-match caching filter may produce a response in this way, which would effectively skip any post-match request filters as well as post-match response filters. Note however that a responses produced in this manner would still be processed by the pre-match response filter chain.

Specified by:

filter in interface ContainerRequestFilter

Parameters:

requestContext - request context.

Throws:

IOException - if an I/O exception occurs.

See Also:

PreMatching