Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
Thanks, good to know.

AFAIK any change that goes beyond the current (Closed Source) TCK for Java EE 8 will need new Spec/API and TCK for JAX-RS 2.2 or whatever the next version shall be. And with it likely a split of namespaces between "legacy" (Java EE 8) and new elements under the Jakarta EE process.

Werner





On Mon, Sep 10, 2018 at 4:20 PM Santiago Pericas-Geertsen <santiago.pericasgeertsen@xxxxxxxxxx> wrote:

 Just to second what Markus has said, there have been NO API additions to JAX-RS 2.1.1 and the 2.1 TCK signature tests pass on 2.1.1. 

— Santiago 

On Sep 9, 2018, at 11:13 AM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

JAX-RS 2.1.1 _did not_ add any features due to EF's target to simply repeat the feature set of Java EE 8. In JAX-RS 2.2 (planned for later this year) I have added a complete new API which covers a feature which had been there already existing in Jersey, but was hidden behind a native API. If a package name change is needed, the EMO ("Eclipse Legal") will tell us. Until then, we just keep the package names as-is.
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil
Sent: Sonntag, 9. September 2018 15:09
To: Jakarta EE community discussions
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
 
Did you add an entirely new element (interface or other) to the JAX-RS API that wasn’t there before?
 
The discussion still does not seem complete, but from what I heard so far also in the Spec Committee, if JAX-RS 2.1.1 added an entirely new element under javax.ws.rs, basically anything that would go beyond a simple Maintenance Release (MR) in the JCP, then this new element must be introduced under the new namespace (presumably “jakarta.rs” or “jakarta.ws.rs” for consistency)
 
Werner
 
Sent from Mail for Windows 10
 
From: Markus KARG
Sent: Sunday, September 9, 2018 13:18
To: 'Jakarta EE community discussions'
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
 
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.
 
Thanks,

Mihai

On Sun, Sep 9, 2018, 09:31 Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
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
 
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Guillermo González de Agüero
Sent: Sonntag, 9. September 2018 07:49
To: Jakarta EE community discussions
Cc: EE4J PMC Discussions; emo@xxxxxxxxxxx
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
 
Hi Mihai,
 

Just open some issues on https://github.com/eclipse-ee4j/jaxrs-api :)

El dom., 9 sept. 2018 1:54, Mihai A. <amihaiemil@xxxxxxxxx> escribió:
Congratulations!
 
Maybe a silly question, but how can one propose new features for JAX-RS exactly? I have a few ideas, but absolutely no idea who to talk to/how to propose them officialy.
 
Best regards,
Mihai
 
On Sun, Sep 9, 2018, 01:14 Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
The JAX-RS committers proudly announce that JAX-RS 2.1.1 is released and publicly available on Maven Central. :-)
-Markus
 
_______________________________________________
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
_______________________________________________
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

_______________________________________________
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

 
_______________________________________________
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

_______________________________________________
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

Back to the top