Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartabatch-dev] Evolving the jakarta batch standard?
I am sorry if this is a totally dumb question, but where is the current backlog/issues? Are the issues from the JCP days ported over? All I was able to find is this: https://github.com/eclipse-ee4j/batch-api/issues? I certainly remember filing a couple of issues. If needed, I can help port issues over.

To me, this specification is pretty stable. The big ticket items for me are Java based configuration as an alternative to XML and slightly better CDI injection support.

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 2/5/2020 2:05 PM, Scott Kurz wrote:

Hi Martijn,

Good to hear from you.

Yes, this list has been quiet.  

The next hurdle ahead is Jakarta EE 9, but once that is complete we should be ready to move forward and develop a plan (we haven't really started that effort).

So thanks for kicking off the discussion,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

Inactive hide details for Mark Struberg ---02/05/2020 12:07:08 PM---+1 for improvements! I'm here to help.Mark Struberg ---02/05/2020 12:07:08 PM---+1 for improvements! I'm here to help.

From: Mark Struberg <struberg@xxxxxxxxxx>
To: jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>
Date: 02/05/2020 12:07 PM
Subject: [EXTERNAL] Re: [jakartabatch-dev] Evolving the jakarta batch standard?
Sent by: jakartabatch-dev-bounces@xxxxxxxxxxx




+1 for improvements!

I'm here to help.

LieGrue,
strub

PMC member Apache Geronimo BatchEE


> Am 05.02.2020 um 17:59 schrieb Martijn Dashorst <martijn.dashorst@xxxxxxxxx>:
>
> I'm currently working on a project that does a lot of processing in
> steps, and other projects have used our own custom jobs framework
> (written prior to Jakarta Batch's inception), and I might advocate to
> rewriting them to Jakarta Batch. The match between the standard and
> what we are doing looks quite promising.
>
> However, there are many thousands of paper cuts that are bugging me in
> either the implementation we are using (jberet and wildfly), or the
> specification.
>
> First I'd like to hear if there's any interest in improving the batch
> specification, and if so, what are the plans?
>
> I figure that this is the right place for discussing the issues I
> encounter while trying to use the specification, to see if my
> understanding is (in)correct, and possibly improve the spec. However
> the list archive does seem to suggest that traffic on this list is a
> bit slow.
>
> I'd love to hear from the batch community if the specification can be
> improved and figure out in what way that is possible.
>
> Kind regards
>
> Martijn Dashorst
> _______________________________________________
> jakartabatch-dev mailing list
> jakartabatch-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartabatch-dev

_______________________________________________
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartabatch-dev





_______________________________________________
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartabatch-dev



-- 
Reza Rahman
Principal Program Manager
Java on Azure

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

Back to the top