Alasdair Nottingham On Oct 1, 2019, at 4:59 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
Kevin Sutter wrote on 10/1/19 1:15 PM:
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 agree, that should probably be on the list.
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?
At the moment it isn't marked "proposed optional". We had hoped to
update it rather than prune it, but if there's no longer any
interest in it we could consider pruning it as well. We need to
decide what the pruning process is for Jakarta EE.
+1 I think a new spec for the use case given it was going REST over JMX makes sense. I don’t know of much usage from the customer apps I have seen.
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?
Mostly the latter. CORBA and SOAP usage is dropping significantly,
but XML is still widely used. Mail needs Activation, which is why
it's still there.
I still see a lot of SOAP out there. Even JAX-RPC is used by a significant existing application estate. I think we need to show a future for these SOAP apps in Jakarta EE and pulling in the JAX-WS APIs is the right approach.
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?
It just has to not disrupt Jakarta EE releases. If the work to
restructure the TCKs can be done on a branch and kept in sync with
the work to update the TCKs for Jakarta EE 9, that would be fine,
but that's even more work.
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)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
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 "jakartaee9.md" deleted by Kevin
Sutter/Rochester/IBM]
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________jakartaee-platform-dev mailing listjakartaee-platform-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|
