Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Some guidelines for Maintenance Releases (MRs) of Java EE 8 Specifications
Hi Will,
 
thank you very much for clearing this aspect up. I knew we must have understood something wrong.
A change of existing package-names is unthinkable and the effect on consistency would be unpredictable.
 
Best Regards,
Alex
 
 
Gesendet: Dienstag, 09. Januar 2018 um 00:24 Uhr
Von: will.lyons@xxxxxxxxxx
An: ee4j-community@xxxxxxxxxxx
Betreff: Re: [ee4j-community] Some guidelines for Maintenance Releases (MRs) of Java EE 8 Specifications

I agree with Bill's replies.

Here is what the EE4J FAQ says about the javax.* namespace:

Will EE4J use javax package names?
We recognize this is important to compatibility. We have not yet formalized the plan, but we intend to enable use of existing javax package names to provide compatibility. We also intend to enable extension of existing javax namespaces (e.g. javax.servlet.*) to provide continuity and enable evolution of existing APIs. Our current expectation is that net new packages will use a different namespace naming convention.

Will
 
On 1/8/18 4:56 PM, Bill Shannon wrote:
Werner Keil wrote on 01/ 8/18 01:40 PM:
Will,
 
Thanks for the update.
 
Can you tell us what this means for backward-compatibility and ease of adoption?
 
>   Oracle does not recommend or support use the JCP process for any future Java EE 8 functional enhancements.
effectively means it does not support the use of the javax.* namespace either.
No, that's not what it means.  Please see the EE4J FAQ.
 
What does that mean for JSON-B (Yasson 1.1 still claims to implement JSR 367 without change) or more drastically EclipseLink 3.x? https://projects.eclipse.org/projects/rt.eclipselink/releases/3.0.0
 
There are 3 quarterly releases planned for EclipseLink 3. At least 3.0.0 as  Major release (API breakage) 
What does that mean for JPA? The relatively small MR of JPA 2.2 would not offer  Full Java SE 9 compatibility for EclipseLink 3 without an API upgrade likely also something like JPA 3 or at least something that declares full Java SE 9 modules. 
Where is this supposed to happen and under what package name, javax.persistence or something else?
Functional enhancements of these APIs should occur as part of the EE4J project, using whatever process is defined there.  Again, see the EE4J FAQ.



 
 
  
_______________________________________________
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

_______________________________________________ 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

Back to the top