I declare this BALLOT complete. There are not enough +1 votes to include JNoSQLin Jakarta EE 11 at this time.
Thank you to everyone who shared constructive feedback in the DISCUSSION portion of this matter.
I hope the feedback given during the DISCUSSION thread is helpful to get this important technology to a place where it can be included in the Jakarta EE Platform.
Here is the final tally.
Jakarta NoSQL Vote count (see details in spreadsheet)
Binding
+1: 2
0: 6
-1: 7
Non-binding
+1: 1
0:
-1: 1
| edburns@xxxxxxxxxxxxx | office: +1 954 727 1095
| Calendar Booking:
https://aka.ms/meetedburns
|
| Please don't feel obliged to read or reply to this e-mail outside
| of your normal working hours.
|
| Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Arjan Tijms via jakartaee-platform-dev
Sent: Monday, August 14, 2023 5:11 PM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] [BALLOT] Include Jakarta NoSQL in EE 11
0 (binding)
I know this has been mentioned before, but I still have doubts about the need to have a separate entity type. Support for NoSQL is certainly a very good idea, but maybe a tighter cooperation with Jakarta Persistence is possible?