[
https://issues.jboss.org/browse/JBIDE-16753?page=com.atlassian.jira.plugi...
]
Xavier Coulon updated JBIDE-16753:
----------------------------------
Description:
(See JAX-RS 2.0 spec., Chap.6)
As far as server-side JAX-RS is concerned, 4 types of interceptors should be support in
the tooling:
{code}
public interface ContainerRequestFilter {
void filter(ContainerRequestContext requestContext) throws IOException;
}
public interface ContainerResponseFilter {
void filter(ContainerRequestContext requestContext,
ContainerResponseContext responseContext) throws IOException;
}
public interface ReaderInterceptor {
Object aroundReadFrom(ReaderInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
public interface WriterInterceptor {
void aroundWriteTo(WriterInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
{code}
User-defined Interceptors should implement one or more of those interfaces and be
annotated with {{@Provider}}
Optionally, user-defined ContainerRequestFilter can also be annotated with
{{@PreMatching}} to indicate that it should be executed upon receiving a client request
but before a resource method is matched
was:
See Spec Chap.6
As far as server-side JAX-RS is concerned, 4 types of interceptors should be support in
the tooling:
{code}
public interface ContainerRequestFilter {
void filter(ContainerRequestContext requestContext) throws IOException;
}
public interface ContainerResponseFilter {
void filter(ContainerRequestContext requestContext,
ContainerResponseContext responseContext) throws IOException;
}
public interface ReaderInterceptor {
Object aroundReadFrom(ReaderInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
public interface WriterInterceptor {
void aroundWriteTo(WriterInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
{code}
User-defined Interceptors should implement one or more of those interfaces and be
annotated with {{@Provider}}
Optionally, user-defined ContainerRequestFilter can also be annotated with
{{@PreMatching}} to indicate that it should be executed upon receiving a client request
but before a resource method is matched
Provide support for server-side Filters and Interceptors
--------------------------------------------------------
Key: JBIDE-16753
URL:
https://issues.jboss.org/browse/JBIDE-16753
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: webservices
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta1
(See JAX-RS 2.0 spec., Chap.6)
As far as server-side JAX-RS is concerned, 4 types of interceptors should be support in
the tooling:
{code}
public interface ContainerRequestFilter {
void filter(ContainerRequestContext requestContext) throws IOException;
}
public interface ContainerResponseFilter {
void filter(ContainerRequestContext requestContext,
ContainerResponseContext responseContext) throws IOException;
}
public interface ReaderInterceptor {
Object aroundReadFrom(ReaderInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
public interface WriterInterceptor {
void aroundWriteTo(WriterInterceptorContext context)
throws java.io.IOException, javax.ws.rs.WebApplicationException;
{code}
User-defined Interceptors should implement one or more of those interfaces and be
annotated with {{@Provider}}
Optionally, user-defined ContainerRequestFilter can also be annotated with
{{@PreMatching}} to indicate that it should be executed upon receiving a client request
but before a resource method is matched
--
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