[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9
|
After further review,
I may need to modify my vote... Or, at least, I need clarification...In previous mailing
list posts (https://www.eclipse.org/lists/jakartaee-platform-dev/msg00944.html)
and on this morning's Platform call, I had made the assumption that the
items in the Pruning list related to interop and the 2.x and 1.x client
views were outlined in the EJB 3.2 Optional Feature Specification:-
Jakarta Enterprise Bean interoperability
-
Jakarta Enterprise Bean 2.x and 1.x client view
As
I was further reviewing Kenji's -1 votes on these two items and yet he
voted +1 on the Entity Bean removal, I started to dig a bit more. I
talked this over with my EJB lead and now we're wondering what exactly
is meant by the two bullets above.
Do
they refer to the Entity Bean Interop and the Entity Bean 2.x/1.x client
APIs as defined by the EJB 3.2 Optional Feature Specification? This
is what my assumption was, but maybe that assumption was incorrect.
Or,
do they refer to the EJB 2.x API Group as defined by Table 18 in the EJB
3.2 Core Spec? This EJB 2.x API Group lists out the Session Bean
component, the client views, and the services affected (including RMI/IIOP
interop. If it's this latter definition, then this is a larger impact
to both implementations and customer applications. This API Group
is not marked Optional, it's a Required feature for EJB.
Since
Bill submitted the original list for removal, maybe we need clarification
from him. And, once we get clarification, maybe we need to re-vote
(unless I was the only one confused). Thanks!
On
hindsight, it may have been worthwhile to explicitly call out which EJB
API Groups are being discussed for pruning. The Table 18 in Section
16 is quite clear on the intent for each API Group, and whether it's currently
Required or Optional.
---------------------------------------------------
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/kevinwsutterFrom:
"Kevin
Sutter" <sutter@xxxxxxxxxx>To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>Date:
11/25/2019
16:44Subject:
[EXTERNAL]
Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta
EE 9Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
+1
I know that the Enterprise Web Services specification is kind of tied to
the JAXB/JAX-WS discussion in the Add vote. But, since I would like
to see none of this in Jakarta EE 9, I'm voting a +1 for all of this pruning
on the hopes that it might help influence the Add Specification discussion.
---------------------------------------------------
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: "Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To: jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 11/17/2019
10:56
Subject: [EXTERNAL]
[jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta
EE 9
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
See
previous email for context.
All
committers please vote on this proposal for specifications to be pruned
from the Jakarta EE 9 platform specifications.
The
following specifications will be *removed* from Jakarta EE 9 Full profile
specification.
-
Jakarta XML Registries JSR 93
-
Jakarta XML RPC JSR 101
-
Jakarta Deployment JSR 88
-
Jakarta Management JSR 77 note this was not optional or deprecated in Java
EE 8
-
Jakarta Enterprise Bean entity beans – Note this is old style CMP and
BMP entity beans NOT JPA Entities
-
Jakarta Enterprise Bean interoperability
-
Jakarta Enterprise Bean 2.x and 1.x client view
-
Jakarta Enterprise Web Services JSR 109
Please
vote by reply with +1, 0, -1 in accordance with the Eclipse Development
Process.
Thanks
Steve_______________________________________________
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