Unfortunately this is not the EFs official policy. According to EF president Mike Milinkovic, all EE4J API projects shall NOT force features from vendors, but instead shall only wrap existing features under a common hood. What I did is adding feature to API AND to Jersey parallel, and encouraged other vendors to follow. -Markus From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Mihai A.
Sent: Sonntag, 9. September 2018 10:48
To: Jakarta EE community discussions
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central Well, from my point of view, the API should add features and force implementors to keep up. If we only ask for a feature from RestEasy, then the whole point of JAX-RS is gone... but I guess that's a neverending discussion. Mihai In fact JAX-RS is just an API, not a product. So unless some implementations (like Jersey, CXF, RestEasy, etc.) already support your wanted feature, it might be a good idea to contribute your wanted feature to one of that products first. This makes it much easier for the vendors to agree to your feature proposal in the API as they do not have to invest their own ressources or at least have a guiding blue print (RI) then. -Markus Hi Mihai, _______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
|
