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

I'm not sure if only Platform commiters can finally vote. If not, my vote is +1.

In Java EE 8, remote EJB through RMI-IIOP protocol was made optional. Can we also remove that requirement? At least WildFly and Payara already offer alternative implementations via HTTP.

On Sun, Nov 17, 2019 at 6:33 PM carlos andres de la rosa <kusanagi12002@xxxxxxxxx> wrote:
+1

On Sun, 17 Nov 2019, 17:56 Steve Millidge (Payara), <steve.millidge@xxxxxxxxxxx> wrote:

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