Graham,
I have filed a post-2.1 reminder so the Expert Group can discuss your proposal _after_ Java EE 8.
If anybody is really interested in this spec change, please login to the spec JIRA and VOTE. ☺
https://java.net/jira/browse/JAX_RS_SPEC-518
As a community representative I really love all user input and ideas like this, but the discussions have to go in the right place. Jersey forum is not, as it is product-specific. JAX-RS JIRA is exactly where proposal are in good hands, as it is vendor-neutral and provides a voting system. So can we finally move this thread over there please…? :-)
-Markus (JAX-RS Expert Group)
Von: Graham Leggett [mailto:minfrin_at_sharp.fm]
Gesendet: Montag, 12. Oktober 2015 14:46
An: users_at_jersey.java.net<mailto: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
—