Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [jakartabatch-dev] Jakarta Batch + CDI integration POLL results

Hi Reza,

There were 8 more responses.    I didn't bother sending out a final email since the net was unchanged:  a majority preference for

    Option 3
    A new direction - make everything a CDI bean

Though I had updated the table in the tracking issue: https://github.com/eclipse-ee4j/jakartaee-platform/issues/441

Thank you to all who helped with the discussion and then Reza especially for publicizing the poll.

------------------------------------------------------
Scott Kurz
WebSphere / Open Liberty Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

Inactive hide details for "Reza Rahman" ---01/03/2022 06:05:08 PM---Was the final tally ever shared? Just wanted to know if we "Reza Rahman" ---01/03/2022 06:05:08 PM---Was the final tally ever shared? Just wanted to know if we got a few  more votes in the end.

From: "Reza Rahman" <reza_rahman@xxxxxxxxx>
To: "jakartabatch developer discussions" <jakartabatch-dev@xxxxxxxxxxx>, "jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 01/03/2022 06:05 PM
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] [jakartabatch-dev] Jakarta Batch + CDI integration POLL results
Sent by: "jakartaee-platform-dev" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>



Was the final tally ever shared? Just wanted to know if we got a few more votes in the end.

On 12/5/21 3:39 PM, Scott Kurz wrote:


    Reza,

    Please by all means, try to push for more results.  Maybe there's a way to publicize via Jakarta One this week?

     If we get any more I'll update the PR capturing the details.  

    I'd just sent that out noticing the count seems to have stopped (it's still at 63, same as when I sent the email).

    Thanks,
    ------------------------------------------------------
    Scott Kurz
    WebSphere / Open Liberty Batch and Developer Experience
    skurz@xxxxxxxxxx
    --------------------------------------------------------

    Inactive hide details for "Reza Rahman" ---12/04/2021 12:35:46 PM---Scott, It’s OK to move forward with status quo. Shouldn’t"Reza Rahman" ---12/04/2021 12:35:46 PM---Scott, It’s OK to move forward with status quo. Shouldn’t we wait a bit for the results though? Less

    From:     "Reza Rahman" <reza_rahman@xxxxxxxxx>
    To:     "jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>, "jakartabatch-dev@xxxxxxxxxxx" <jakartabatch-dev@xxxxxxxxxxx>
    Date:     12/04/2021 12:35 PM
    Subject:     [EXTERNAL] Re: [jakartabatch-dev] [jakartaee-platform-dev] Jakarta Batch + CDI integration POLL results
    Sent by:     "jakartabatch-dev" <jakartabatch-dev-bounces@xxxxxxxxxxx>




    Scott,

    It’s OK to move forward with status quo.

    Shouldn’t we wait a bit for the results though? Less than a hundred votes is very low still and I was going to do a final push since my understanding is that the votes are open until December 15?

    Can you let me know so I can plan accordingly?

    Reza Rahman
    Jakarta EE Ambassador, Author, Blogger, Speaker

    Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
     

    From:     jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Scott Kurz <skurz@xxxxxxxxxx>
    Sent:     Thursday, December 2, 2021 10:19 AM
    To:     jakartabatch-dev@xxxxxxxxxxx; jakartaee-platform-dev@xxxxxxxxxxx
    Subject:     [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.


GIF image

Back to the top