Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartabatch-dev] Old Java Batch issues from java.net reopened in github eclipse-ee4j/batch-api

I will help get the word out on these.

On a separate note, do you think any of the remaining Jakarta EE 9 work could be crowdsourced or is it too intricate for that at this point?

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.

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: Scott Kurz <skurz@xxxxxxxxxx>
Date: 7/20/20 7:03 AM (GMT-05:00)
To: jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>
Subject: Re: [jakartabatch-dev] Old Java Batch issues from java.net reopened in github eclipse-ee4j/batch-api

I think that's a good start to frame the next "big ticket" goals.

I'd add: "Add support for multiple readers, processors, writers, within a chunk step." (just opened as #107) :

I could also see work on batch property injection adding up to a major item in and of itself.. assuming we were to work on:

#95 (provide batch property value from an earlier portion of execution) and
#82 (property + beanVal
#43 (properties from well known types)

and maybe method/ctor injection. I think adding a Java job definition API would (should) force us to revisit and discuss batch properties in detail.

---
We still have to get EE 9 shipped, so I was envisioning maybe a more formal "kickoff" when done.... not to say we can't discuss before but just noting.

------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------


Inactive hide details for Reza Rahman ---07/19/2020 01:58:50 PM---The two big ticket changes I see are: * Aligning Jakarta BatcReza Rahman ---07/19/2020 01:58:50 PM---The two big ticket changes I see are: * Aligning Jakarta Batch to take better advantage of CDI.

From: Reza Rahman <reza_rahman@xxxxxxxxx>
To: jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>
Date: 07/19/2020 01:58 PM
Subject: [EXTERNAL] Re: [jakartabatch-dev] Old Java Batch issues from java.net reopened in github eclipse-ee4j/batch-api
Sent by: jakartabatch-dev-bounces@xxxxxxxxxxx





The two big ticket changes I see are:

* Aligning Jakarta Batch to take better advantage of CDI.
* Add a Java configuration API as an alternative to XML.

My feeling is that both issues are relatively well understood but have not really been discussed or analyzed in detail just yet. Is that a fair take? I see the CDI alignment items come up a few times in the issues but no mention of the Java configuration API somehow. Is it worth it to make sure both of these items are (more) prominently represented in the issues somehow?

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.

On 7/15/2020 1:42 PM, David Follis wrote:



Back to the top