[ 
https://issues.apache.org/jira/browse/CXF-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666311#comment-13666311
 ] 

Sergey Beryozkin commented on CXF-5038:
---------------------------------------

It is a good idea but note we already have a support for it. Up to CXF 2.7.x 
you can use CXF ParameterHandler, though it only works on the server side. From 
CXF 2.7.x - use JAX-RS 2.0 ParameterConverterProvider  
                
> More flexible QueryParams
> -------------------------
>
>                 Key: CXF-5038
>                 URL: https://issues.apache.org/jira/browse/CXF-5038
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Vincent Tremblay
>
> It would be useful to be able to handle how a beans are traduced into 
> QueryParams.
> I can see something like a ParametersWriter<T> and a ParametersReader<T> to 
> achieve this goal.
> Ex.
> Let's say that you have the following method:
> @GET
> @Path("/resource")
> public void doSomething(@QueryParam ComplexObject);
> You could declare a ParametersWriter that can handle the creation of the 
> parameters:
> public class ParametersWriter<ComplexObject> {
>     
>     writeParameters(ComplexObject object, Map<String, List<Object>> params) {
>          params.put("filter", Arrays.asList(...,...));
>          params.put("query", Arrays.asList(...));
>     }
> }
> Then, on the server side, you could have a ParametersReader<ComplexObject> 
> that can rebuild the object from the request's parameters.

--
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

Reply via email to