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.
No, that's not what it means. Please see the EE4J FAQ.
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