Your understanding is correct. I mean it won't be possible to create new specs that fall into the same category as the existing ones (part of the Java official API). That was one of the biggest values of Java EE for me.
Even if we come to the conclusion that can't use that packages for new specs, I miss a way to add functionality to the standard API. MicroProfile did it with Config and JSR 382. I wonder if the same path should be the way for EE4J: moving to the JCP *specific* components that should be part of the whole Java API.
On 16 Jan 2018, at 21:39, Guillermo González de Agüero wrote:
> What we are discussing here is not a replacement but the abandonment
> of the "Standard Enterprise API".
Can you please explain what you mean?
My understanding is that the existing APIs do not change,
but fo new APIs under the umbrella, the (top level) package names
will be different from what they were.
_______________________________________________
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
