Quantcast

Parameter converters in WebResourceFactory

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Parameter converters in WebResourceFactory

Harald Wellmann
Working with WebResourceFactory to build a Java client for a given
JAX-RS API, I'm currently blocked by the fact that parameter converters
used by the server do not get picked up by the WebResourceFactory or the
JAX-RS client.

This issue has been reported as a bug in
https://java.net/jira/browse/JERSEY-3248 - I think it is rather a
feature request, since javax.ws.rs.ext.ParamConverter.toString(T) is
clearly marked as "reserved for future use" both in JAX-RS 2.0 and the
current 2.1 draft.

Anyway, I've started hacking jersey-proxy-client to implement a
solution, which might evolve into an official contribution.

Before going into any technical details, I would like to ask how to proceed:

- Is the project team ready to review and accept pull requests at the
moment?

- Which should be the target branch for a pull request? (My project
can't wait for JAX-RS 2.1, so I'd need a solution for JAX-RS 2.0.)

Regards,
Harald

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Parameter converters in WebResourceFactory

Pavel Bucek-2
Hi Harald,

please see inline.


On 07/04/2017 14:07, Harald Wellmann wrote:

> Working with WebResourceFactory to build a Java client for a given
> JAX-RS API, I'm currently blocked by the fact that parameter
> converters used by the server do not get picked up by the
> WebResourceFactory or the JAX-RS client.
>
> This issue has been reported as a bug in
> https://java.net/jira/browse/JERSEY-3248 - I think it is rather a
> feature request, since javax.ws.rs.ext.ParamConverter.toString(T) is
> clearly marked as "reserved for future use" both in JAX-RS 2.0 and the
> current 2.1 draft.
>
> Anyway, I've started hacking jersey-proxy-client to implement a
> solution, which might evolve into an official contribution.
>
> Before going into any technical details, I would like to ask how to
> proceed:
>
> - Is the project team ready to review and accept pull requests at the
> moment?

that depends on the nature of the pull request. We are considering them
on case-by-case basis, aligning them by the priorities and the amount of
time required for the review.

Please understand that we are quite busy with JAX-RS 2.1 related work,
so the response time on pull request is currently not so good from our
side, especially when they are not that related to our current objective
- deliver Java EE RI.

>
> - Which should be the target branch for a pull request? (My project
> can't wait for JAX-RS 2.1, so I'd need a solution for JAX-RS 2.0.)

currently, its only master. branch 2.x was recently merged to the master.

Having said that, I wouldn't expect Jersey 2.25.x release (JAX-RS 2.0)
before Jersey 2.26 is out, unless there is some justifiable reason to do it.

Thanks and regards,
Pavel

>
> Regards,
> Harald
>

Loading...