Graham,
understood.
So you want me to propose to the Expert Group that they decide in a democratic process to add such an “enable alternative resolution strategy” option switch, and that the strategy shall be like this:
· First find matching resource class
· Then find matching method annotation on that resource class
· Then find 100% literal path matches
· Then find “starts with” path matches
· Then find by regex
Right?
You’re also ok with the fact that this leads to the situation that Java EE 8 will come with no new version of JAX-RS because none of the vendors can provide this strategy out of the box and Spec Lead Oracle already said loud and clear that they definitively will never touch this strategy (hence effectively leading to JSR 370 to completely fail)?
See, you’re right with all you say, but the truth is that if Oracle says “no” then this means “no”.
-Markus
Von: Graham Leggett [mailto:minfrin_at_sharp.fm]
Gesendet: Montag, 12. Oktober 2015 14:46
An: users_at_jersey.java.net
Betreff: [Jersey] Re: Discussion about re-opening a bug: JERSEY-2942
On 12 Oct 2015, at 2:21 PM, Markus Karg <karg_at_quipsy.de<mailto:karg_at_quipsy.de>> wrote:
thank you for your kind input, but see, pointing out that others did bad things in the past should not be an excuse to also do bad things.
I don’t follow, I made no mention about people doing bad things in the past.
What I pointed out is that the solution is simple - keep the existing backward compatible behaviour so the whole world doesn’t unexpectedly break.
Then, add a -D switch to enable the “fixed” behaviour, and default that switch to off.
The guys who upgrade expecting everything to still work find that everything still works. The guys who need the fix enable to switch and they get their fix. Everyone is happy.
Regards,
Graham
—