@PreMatching public class AcceptParameterHttpPreprocessor extends Object implements ContainerRequestFilter
Enables content negotiation through a query parameter, instead of the Accept Header.
To enable this feature, use the context-param in web.xml:
So, in a request like
the application/xml media type will received the highest priority in the content negotiation.
In the cases where the request contains both the parameter and the Accept header, the parameter will be more relevant.
It is possible to left the
param-value empty, what will cause the processor to look for an accept parameter.
|Constructor and Description|
Create a new AcceptParameterHttpPreprocessor.
|Modifier and Type||Method and Description|
Filter method called before a request has been dispatched to a resource.
public AcceptParameterHttpPreprocessor(String paramMapping)
paramMapping- The name of query parameter that will be used to do the content negotiation
public void filter(ContainerRequestContext request) throws IOException
Filters in the filter chain are ordered according to their
class-level annotation value.
If a request filter produces a response by calling
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.
Copyright © 2019 JBoss by Red Hat. All rights reserved.