Markus KARG

Kindly asking everybody to vote on this PR. Thanks! :-)

> What is the real benefit in natively supporting `java.nio.file.Path` when you have `java.nio.file.Path#toFile`? Just trying to understand the rationale here. Besides migrating JAX-RS's API to modern Java, it mostly...

> > > > What is the real benefit in natively supporting `java.nio.file.Path` when you have `java.nio.file.Path#toFile`? Just trying to understand the rationale here. > > > > > >...

> From an API perspective, I understand that `Path` may be desirable in some cases (yet, this is a bit of a weak argument IMO). From an implementation perspective, which...

Now that we all have exchanged our personal opinions, in the name of modern Java, I do beg all committers to vote +1. Thanks.

As the PR is finally authored, and as Jersey is already implementing this feature, can anybody please tell me a good reason why we not simply merge this into the...

Kindly asking to resume this discussion. This PR would help to let JAX-RS look more modern, it is already supported by Jersey, and it would be just straight forward. Please...

The point of my question simply is: Neither the spec nor the JavaDocs explicitly mandate that the result of `.register()` and `.property()` MUST update the original object, but only says,...

> > As a general rule, for each JAX-RS component class there can be at most one registration — class-based or instance-based — configured at any given moment. Implementations MUST...

@jamezp Isn't the problem obvious? See: ```java Client client = ClientBuild.newClient(); // client refers to object 1 initially, which is immutable client.property("MyProperty", "MyValue") // object 1 is untouched, property() returns...