From: Werner Keil <werner.keil_at_gmail.com>
Date: Fri, 25 Jan 2013 10:36:11 +0100

Markus/all,

Thanks for your input.
I was also quite indifferent when I saw the 236 presentation in the EC F2F
recently.

It shows redundant aspects of things other JSRs just as of now are also
working on. A "Batch" Mode most notably, though Linda said, it could
theoretically be used by those implementing Java Batch (JSR 352) but
wouldn't replicate Batch as such.

I believe, we agreed, Batch should not be in the Web Profile either, so
given all the functionality similar to Batch, EJB or even WebSockets (a
more modern approach to Async, makes what 236 tried to address nearly a
decade ago also less important in the new decade[?]) I would not add it to
WP IMHO.

Werner

On Fri, Jan 25, 2013 at 8:30 AM, Markus Eisele <myfear_at_web.de> wrote:

> Hi,
>
> > At this point, we expect that JSR-236 will meet our target dates for
> > inclusion into Java EE 7. JSR-236 is an obvious candidate for inclusion
> > in the full Java EE Platform, and we believe that it should be.
>
> Congrats to the EG :) Very good news!
>
> > Pleases let us know:
> >
> > (1) Whether you see any reason that JSR 236 should not be included in
> > the full platform?
>
> No.
>
> > (2) Whether you think that JSR 236 should also be included in the Web
> > Profile?
>
> Very undecided myself.
> pro: No EJB Timer service in WP, so there might be a need for some
> lightweight timer driven things which could be done with 236
>
> con: WP is getting too big ...
>
> As of today I would NOT include it in the WP.
>
> - M
>