[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] Deprecate JSR-352 and rework JSR-236
|
I agree that while discussion on what the requirements should be for the platform to support batch (or not) belong on this list, discussions about how to evolve Jakarta Batch would be better moved to the Batch mailing list.
The Jakarta Batch (successor of JSR 352) mailing list address is: jakartabatch-dev@xxxxxxxxxxx and you can subscribe here: https://accounts.eclipse.org/mailing-list/jakartabatch-dev
With EE 8 recently completed and EE 9 focused on package rename, this list has been quiet, but this is a good time to start looking forward at EE 10 and new function.
We've long recognized the opportunity to have a better CDI+Batch integration. As Werner pointed out, the history of reaching a middle ground with SpringBatch took us down a compromise path of omitting this integration from the core spec... though I believe Apache BatchEE and JBeret implemented some level of integration (the details of which I forget though).
But anyway, your ideas on bean integration and cloud enablement sound interesting, so hopefully we can continue the discussion over in the batch list.
Thanks,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Compute Grid
Development and Level 3 Team Lead
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102544
skurz@xxxxxxxxxx
--------------------------------------------------------
Hamed Hatami ---12/02/2019 01:53:27 PM---I also hate the spring so just focus on Java EE context to be aligned with the best for the future
From: Hamed Hatami <hamedhatami2012@xxxxxxxxx>
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 12/02/2019 01:53 PM
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] Deprecate JSR-352 and rework JSR-236
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
I also hate the spring so just focus on Java EE context to be aligned with the best for the future
On Mon, 2 Dec 2019, 17:08 Tibor Digana, <
tibordigana@xxxxxxxxxx> wrote:
Spring is not EE. Pls understand it that Spring is your competitor!!!
Don't mind about the Spring and my advice forget Spring and take your own way.
They will try to support EE API in Pivotal but still Spring is not on your side.
On Mon, Dec 2, 2019 at 4:50 PM Werner Keil <werner.keil@xxxxxxx> wrote:
Well maybe because for Batch there just isn't so much demand to add new features or even recreate everything from scratch? ;-)
Especially Jakarta Batch was shaped and inspired as much by the "OSS" de facto standard Spring Batch as no other spec I could think of, so it may be there is no need for change or innovation in this area.
Spring Batch https://spring.io/projects/spring-batch is still at version 4.2.0 while most of the other Spring stack are version 5 now, so that shows, in the Spring platform it also is not so important any more.
Werner
Gesendet: Montag, 02. Dezember 2019 um 16:41 Uhr
Von: "Tibor Digana" <tibordigana@xxxxxxxxxx>
An: "jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>
Betreff: Re: [jakartaee-platform-dev] Deprecate JSR-352 and rework JSR-236
Hi Werner,
I don't know who should be told more in project team and lead.
The frequency of the emails is small in dev mailing list, so I guess everybody can find the spare time to read all emails.
The OSS was created to get critical reactions from the users community. This is wanted and if the Jakarta would not change and listen then this project will die. Therefore it must be their primary wish of the team leads to listen all the emails and I should not be a postman.
Cheers
Tibor17
On Mon, Dec 2, 2019 at 3:42 PM Werner Keil <werner.keil@xxxxxxx> wrote:_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev