[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] EE4J Project Proposals
|
If that's true, honestly it's good news overall. It enables keeping both the Java EE name and javax packages for everything.
The problem is that I don't know how this actually alignes with Oracle and other EE4J expectations. The impression I get is neither is keen on the JCP.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Guillermo González de Agüero <z06.guillermo@xxxxxxxxx>
Date: 11/25/17 3:42 PM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
The September EC minutes somewhat say that existing specs will continue to use the JCP:
https://jcp.org/aboutJava/communityprocess/ec-public/materials/2017-09-28/JCP-EC-Meeting-Minutes-September2017.html
Perhaps that's Oracle idea for granting javax packages on donated specs (which would work also for new ones).
Regards,
Guillermo González de Agüero
What's also weird about JAX-RS is, that it was seemingly "forgotten" when all of Java EE 8 (and earlier JSRs) moved to a new place under
What is not mentioned in the proposals of either, but seems far more important IMO than whether it's called "Eclipse RESTful Web Services API for Java", "JAX-RS" or something else is backward compatibility with the Java EE 8 or 7 versions of these APIs. Is the new follow-up API allowed to stay under "
javax.ws.rs" or immediately forced to refactoring into something else? (like "
ee4j.ws.rs", "ee.<something>.
ws.rs" or e.g. "
org.eclipse.ws.rs" just to mention some hypothetical examples)
Werner
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community