[jakartabatch-dev] Evolving the jakarta batch standard?

[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