These are the final results of the JSR Renewal Ballot for JSR #350. The EC has not approved this ballot.

JSR350

StageJSR Renewal Ballot

Ballot durationApr 28, 2015 to May 11, 2015

Special Vote Instructions

Over the past year the expert group has made progress defining the APIs for State Management, they have gone through several iterations and are at a point where an initial reference implementation should be created to further refine and flesh out the APIs. That said the EG has struggled defining a concrete use case that validates the goal of this JSR, the high level design and the API design. This was more an issue of some key people leaving the EG and losing the context they had that started the JSR and their domain expertise. The EG took a break to focus on other pressing individual responsibilities but intents to resume meeting during this calendar year. At that time the group as currently constituted will revisit the use case and apply the API design to it. We do feel there is a need, and value, for consumers of state to be able to express their requirements at runtime and have pluggable providers fulfill these requirements.

Votes

EC

Arm Limited

Azul Systems, Inc.

Credit Suisse

Eclipse Foundation, Inc

Ericsson AB

Freescale Semiconductor

Fujitsu Limited

Gemalto M2M GmbH

Goldman Sachs & Co.

Hazelcast

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

London Java Community

Magnusson Jr, Geir

MicroDoc

Oracle

Red Hat

SAP SE

Software AG

SouJava

TOTVS

Twitter, Inc.

V2COM

Vote Log

EC

On 2015-04-29 Arm Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2015-04-29 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2015-04-29 Red Hat voted No with the following comment:
The state management and persistence space still vastly evolving. With the expert group struggle during the lifetime of the EG to identify key use cases within Java EE and beyond for such API, Red Hat still thinks that standardisation is premature and a risk. We would rather see the energy of the expert group focused on building an open source project and community around these ideas to gauge the interest of such abstract and contract driven API in the persistence space. The reference implementation could be such vehicle.
------------------------------------------------------------------------------
On 2015-04-29 Software AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2015-05-05 London Java Community voted No with the following comment:
We don't find their reasons compelling enough and there is not enough public evidence of any meaningful progress.  We'd encourage the participants to form an OSS project around this concept and ensure that it is a real use case that the ecosystem at large wants standardised.
------------------------------------------------------------------------------
On 2015-05-11 Gemalto M2M GmbH voted Yes with no comment.
------------------------------------------------------------------------------
On 2015-05-11 SouJava voted No with the following comment:
This is the second extension, and we expected the EG to actively engage with the community at large to revive this JSR. This has not happened, and there are no signs of public activity in this JSR. Probably this idea is not ready for standardization yet. We suggest that EG experiments with other ways of engaging the community, and maybe when things get more concrete, we can reevaluate these ideas in a new JSR.
------------------------------------------------------------------------------
On 2015-05-11 Intel Corp. voted Abstain with no comment.
------------------------------------------------------------------------------
On 2015-05-11 Fujitsu Limited voted Abstain with no comment.
------------------------------------------------------------------------------
On 2015-05-11 Hazelcast voted No with the following comment:
We're not sure that this problem space is ready to be standardized yet, having a problem finding the real world cases and defining the goals support this opinion. Activity on this JSR is like non existing over the recent past and having previous EG members voting against it doesn't leave a good feeling. We encourage the EG forming an oss project to find the real problem space first.
------------------------------------------------------------------------------
On 2015-05-11 Magnusson Jr, Geir voted No with the following comment:
Doesn't appear to be ready for standardization at this time.
------------------------------------------------------------------------------
On 2015-05-04 TOTVS voted Yes with no comment.
------------------------------------------------------------------------------
On 2015-05-08 Goldman Sachs & Co. voted No with the following comment:
The WG has been diligently discussing this project but the problem space lacks the definition that one or more OSS implementations would add. We would respectfully suggest that the work continues in an OSS project and this JSR be suspended until the need is more clearly defined.
------------------------------------------------------------------------------
On 2015-05-07 IBM voted Abstain with the following comment:
IBM abstains. While we have no objections to the stated goals, the historical lack of progress, the difficulties in defining use cases have inhibited progress on the specification. This indicates this may still be premature to standardize, and we should focus our efforts on other priorities.
------------------------------------------------------------------------------
On 2015-05-11 Ericsson AB voted No with the following comment:
Ericsson does not see the state and the progress of this JSR to be satisfactory.
------------------------------------------------------------------------------
On 2015-05-07 Keil, Werner voted Abstain with the following comment:
After a brief discussion with the Spec Lead and having seen 2 formerly active participants (Red Hat I believe was in the EG, LJC adopted it, see https://java.net/projects/adoptajsr/pages/WhoIsAdoptingJSRs##350_-->_#359) vote against it, I'll abstain.
------------------------------------------------------------------------------
On 2015-05-11 Hewlett-Packard voted No with the following comment:
HP votes No, as this is the second JSR Renewal ballot for this JSR and there has been no discernible progress in the past year.  
------------------------------------------------------------------------------
On 2015-05-11 V2COM voted Abstain with no comment.
------------------------------------------------------------------------------
On 2015-05-11 Freescale Semiconductor voted Abstain with no comment.
------------------------------------------------------------------------------
On 2015-05-11 MicroDoc voted Abstain with the following comment:
MicroDoc abstains, mainly because we think that use cases have changed significantly over the last years. 
------------------------------------------------------------------------------
On 2015-05-11 Credit Suisse voted Abstain with no comment.
------------------------------------------------------------------------------
On 2015-05-11 Twitter, Inc. voted Abstain with the following comment:
We believe this is premature to standardize and encourage the EG to continue the work in an OSS project until things have progress to warrant standardization.
------------------------------------------------------------------------------
On 2015-05-11 Eclipse Foundation, Inc voted Abstain with no comment.
------------------------------------------------------------------------------