Re: [ee4j-community] Use of javax.* in new EE4J projects

[Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxx>]

Hi,

It'd be awesome if JCache can be donated under EE4J and be part of future Java EE versions under Eclipse. My point of view is that JCache is already an existing specification. Oracle announced they plan to allow javax. prefix for current Java EE APIs so the only problem with retaining the package name for JCache is that it's not yet a part of Java EE. But since there has always been the intention of bringing JCache into Java EE I think that Oracle should make an exception and treat the JCache specification in the same way as other specifications that are already part of Java EE, including retaining the package name.

Ondro

2017-11-03 19:07 GMT+01:00 Greg Luck <gluck@xxxxxxxxxxxx>:

Hi

Had a call with Mike today about moving JCache across to EE4J.

We have JCache 1.1 in the JCP review process now and it should be out in a few weeks’ time. So we could consider moving after that point. 

The biggest issue to me is that, at least currently, any new APIs will not be allowed to use javax. Today we use javax.cache. This would mean that JCache 2 would need to change its package name. We have 13 implementations out there and a huge amount of user code that uses javax.cache. This would be an extremely disruptive change.

In our case Oracle is a copyright owner along with myself for the spec. As an owner, Oracle if they wished, should be able to allow JCache 2 to continue to use the javax.cache package even though the process has changed from JCP to the yet unnamed and to be formed Eclipse Community Process.

Interested in anyone’s thoughts on this. 

Regards

Greg Luck

_______________________________________________
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