| [jakartaee-platform-dev] Jakarta Batch + CDI integration POLL results |
I think we can report the results now (though I didn't explicitly list an end date, the responses seem to have stopped):
Total responses: 63
Option 1 - Adopt the current/legacy Platform spec approach 22 % (14/63)
Option 2 - Formalize the Batch Status quo - 22 % (14/63)
| Option 3 - A new direction - make everything a CDI bean 56% (35/63) |
| ---- So I suggest two actions. 1. As mentioned earlier https://www.eclipse.org/lists/jakartaee-platform-dev/msg02989.html, for Batch 2.1 and EE 10 we codify the status quo (go with option 2), since that is essentially already supported by the existing implementations that do offer CDI integration 2. Going forwards we open a platform-level discussion to consider the Option 3, make everything a bean approach winning the majority of votes (which again, REST is considering). For this I opened: https://github.com/eclipse-ee4j/jakartaee-platform/issues/441 And again, a key point this whole discussion has brought up is this should really be a platform-level effort and decision. Romain brought up several challenges/objections which seemed persuasive to me ... so if the Platform wants this badly enough, we'll have to deal with that collectively. |