Skip to main content

[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

Since we're going with the Big Bang approach, I would consider any APIs using the javax namespace as *not* part of Jakarta EE 9.  If there's a good chance that a javax API will evolve, then it should move to the jakarta namespace and be part of Jakarta EE 9.

There may be some dependencies from Jakarta EE 9 on javax APIs (ie. JDBC), but those should be highlighted and documented.

---------------------------------------------------
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:        "kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        11/20/2019 16:22
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to Prune        in        Jakarta        EE 9
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx



Kevin,

 

This is true if we move all API from javax to jakarta name space.

But is it possible that some of APIs will use javax namespace in Jakarta EE 9 ?

 

-Kenji Kazumura

 

 

From:jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] On Behalf Of Kevin Sutter
Sent:
Tuesday, November 19, 2019 11:46 PM
To:
jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject:
Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

In this case, we actually using "prune" to mean "remove".  We want to start fresh and remove APIs that are not needed as we move forward with Jakarta EE.  The javax versions of these APIs will continue to live to support older implementations.  But, we're trying to limit the old baggage that we move forward to Jakarta.  As an example, why go through the effort of the javax->jakarta rename for the J2EE Management API?  This would require updates to the Specs, APIs, TCKs, and Compatible Implementations.  That's a lot of work for no benefit.  That's why we are asking to "prune" or "remove" certain older technologies.

---------------------------------------------------
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:        
"kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx>
To:        
jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        
11/18/2019 21:33
Subject:        
[EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in        Jakarta        EE 9
Sent by:        
jakartaee-platform-dev-bounces@xxxxxxxxxxx


 

Steve,

 

I would like make sure what we vote for.

 

We usually use the word “prune” as  “to make something optional” rather than “to remove” in Java EE specifications.

Is this vote for whether we remove specifications or not ?

 

-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



Back to the top