Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE

["kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx>]

My subset is:

 

- Jakarta XML Registries JSR 93  -> +1

- Jakarta XML RPC  JSR 101        -> +1

- Jakarta Deployment JSR 88       -> +1

- Jakarta Management JSR 77     -> +1

- Jakarta Enterprise Bean entity beans  -> +1

- Jakarta Enterprise Bean interoperability   -> -1

- Jakarta Enterprise Bean 2.x and 1.x client view  -> -1

- Jakarta Enterprise Web Services  JSR 109  -> -1

 

-Kenji Kazumura

 

 

 

From: Kevin Sutter [mailto:sutter@xxxxxxxxxx]
Sent: Tuesday, November 26, 2019 12:55 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Kazumura, Kenji/数村 憲治 <kzr@xxxxxxxxxxx>
Subject: RE: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

Kenji,
Can you please expand on your -1 vote?  Is it just the JSR 109 Enterprise Web Services removal (as some others have indicated)?  Or, is it all of them?

Now is the time to define a Jakarta EE platform that we can promote for future application development.  Most of the technologies listed below in the prune list are already marked deprecated and/or optional.  These technologies can continue to live in the existing javax namespace for existing applications and application servers.  We're just trying to prune/remove some of these older technologies so that we don't have to do the work of moving them forward to the new jakarta namespace.

With your -1 vote, we will need to re-evaluate the ballot for pruning.  We'll need your input to figure out what will be acceptable.  Thanks!

---------------------------------------------------
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/25/2019 03:53
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in        Jakarta EE 9
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

---

 

Hi Kenji,

 

As Alasdair says is there some subset you can agree on for pruning? Also as Bill says in response to my comment on making JAX-WS optional what’s the practical difference between optional in Jakarta EE 9 and available as an updated spec outside of the Jakarta EE 9 full profile?

 

Steve

 

From:jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Alasdair Nottingham
Sent: 24 November 2019 14:34
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

Is there some subset of this list you think could be pruned?

Alasdair Nottingham

 

On Nov 24, 2019, at 12:19 AM, "kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx> wrote:



-1

 

Our customers use some of APIs heavily.

I know some of you insist that these APIs will not evolve and these must be handled by vendors’ products.

But  in order to promote Jakarta EE, I prefer keep some APIs in the specifications (as optional or profile or whatever).  

 

-Kenji Kazumura

 

 

 

From:jakartaee-platform-dev-bounces@xxxxxxxxxxx[mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] On Behalf Of Steve Millidge (Payara)
Sent: Monday, November 18, 2019 1:56 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

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