Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Oracle's position on Jakarta EE 9

Excellent strawman, Bill.  Thanks!

What about Entity Beans?  You mention "client view", but did you also mean to include Entity BMP and CMP Beans?  I'd vote +1 for that pruning as well.

I noticed that you didn't include Jakarta Management in the Pruning list.  The other Stable APIs were included to be pruned (Registries, RPC, and Deployment).  Did you just just forget Management, or is there a reason why you wouldn't include that in your list to be pruned?

Any justification on which Java SE 8 APIs should be moved to Jakarta EE 9 and which ones shouldn't?  Or, was it just gut reaction to usage scenarios?

Agree with postponing the MicroProfile decision until after Jakarta EE 9.

The TCK work could be initiated and completed at any time, right?  Does it have to line up with Jakarta EE releases?

Other than that, I think this is a great start!

Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

From:        Bill Shannon <bill.shannon@xxxxxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        10/01/2019 11:33 AM
Subject:        [EXTERNAL] [jakartaee-platform-dev] Oracle's position on Jakarta EE 9
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

See attached for Oracle's proposal for Jakarta EE 9.  We look forward to
continuing this discussion.
[attachment "" deleted by Kevin Sutter/Rochester/IBM] _______________________________________________
jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top