The clean solution would be to tell people that it was simply wrong that
JAX-RS 1.1 did not encode the slash always and that JAX-RS 2.0 will now fix
that. But this breaks existing applications, what the majority in this forum
(not me!) doesn't want to dare.
> -----Original Message-----
> From: Sergey Beryozkin [mailto:sberyozkin_at_talend.com]
> Sent: Dienstag, 23. Oktober 2012 12:07
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: Why do we need special encodeSlashInPath
> methods again?
>
> On 16/10/12 14:06, Bill Burke wrote:
> > Wouldn't changing resolveTempalte() and build() methods to state that
> > '/' is not encoded and you must encode it manually work just as well?
> > Or is it a backward compatibility issue?
> >
> > We have to provide a way for people to specify path params without
> > encoding the '/', but it just seems silly to have a special method
> for
> > this case.
> >
> Agreed the current solution is not ideal at all. Probably too late
> though to revert. The real concern is, with "/" now getting a prominent
> attention at the API level, what would happen if some other character
> in say the query component will need another special treatment during
> the substitution.
>
> Sergey