Are you saying this is preferable to pivoting on custom media-types? I
don't care for the versioned-URI scheme because it puts the same
resource at multiple URIs and thus the I's are no longer U...
On 04/06/2014 08:58 AM, Bill Burke wrote:
> Resteasy cannot dispatch based on header, but I don't
Resteasy cannot dispatch based on header, but I don't recommend a custom
header anyways. The best practice solution is to use URIs i.e.
/v1.0/api and have your client driven by links. You should also make
your apis and media types backward compatible. Its just good practice
no matter what ty
Hi,
was going through docs on version 2.3.x but couldn't find appropriate answer on
may issue.
I would like to produce versioned api where uri does not change. The idea is to
intercept resource locating before auto match happen and decide which method to
invoke based on some custom header (eq.
Hi,
was going through docs on version 2.3.x but couldn't find appropriate answer on
may issue.
I would like to produce versioned api where uri does not change. The idea is to
intercept resource locating before auto match happen and decide which method to
invoke based on some custom header (eq.
