[jboss-jira] [JBoss JIRA] (WFLY-11242) Provide builtin ParamConverter* classes for multi valued params

[Ron Sigal (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal moved JBEAP-15723 to WFLY-11242:
------------------------------------------

          Project: WildFly  (was: JBoss Enterprise Application Platform)
              Key: WFLY-11242  (was: JBEAP-15723)
         Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
    Fix Version/s: 15.0.0.Alpha1
                       (was: 7.3.0.GA)


> Provide builtin ParamConverter* classes for multi valued params
> ---------------------------------------------------------------
>
>                 Key: WFLY-11242
>                 URL: https://issues.jboss.org/browse/WFLY-11242
>             Project: WildFly
>          Issue Type: Feature Request
>            Reporter: Marek Kopecký
>            Assignee: Ron Sigal
>            Priority: Major
>             Fix For: 15.0.0.Alpha1
>
>
> This is follow up for RESTEASY-1746 and RESTEASY-1566. In these feature jiras, users needs to prepare custom ParamConverter* classes in deployment.
> This feature should provide builtin ParamConverter* universal classes.
> Some PoC is in [this commit|https://github.com/marekkopecky/Resteasy/commit/08e0eb6de20608559371a940d53c41102a6c50ac]
> Suitable annotations for end-point can parametrize converter behaviour. [~ron_sigal]'s proposal:
> {noformat}Maybe annotations in
> >     public <T> ParamConverter<T> getConverter(Class<T> rawType, Type genericType, Annotation[] annotations;
> could be used to generalize. E.g.,
>     public Response conversion1(@QueryParam @Separator("&") List<MultiValueParamBuiltinMyObject1> q);
> Even more general could be something like
>     public Response conversion1(@QueryParam @MultiSyntax(<regular expression/>) List<MultiValueParamBuiltinMyObject1> q) {{noformat}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)