Re: [cu-dev] Proposed features for Concurrency 3 and Jakarta EE 10

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

Thanks! An important feature for us at the time was to limit concurrent throughout. If I’m not mistaken the EJB spec mentions that too.

That’s what might make it a good candidate for the concurrency spec.

Kind regards,

Arjan

On Wednesday, March 17, 2021, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:

+1 for @Pooled. It’s surprisingly useful functionality in performance benchmarks that I have done. I do think it’s slightly lower priority. A lot of people seem to have an initial adverse reaction to the use of object pooling and think it is overkill or actually a performance problem for some reason.

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 Mar 17, 2021, at 11:44 AM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:



Hi,

That list looks very good Steve, thanks! Big +1 from me!

Some of the work has already been done or prepared. E.g. the context propagation that's being developed under MP has an explicitly stated goal to be transferred to Jakarta Concurrency when the time is right. That would be about now then.

The @Asynchronous annotation has been implemented in a CDI version multiple times over in different projects, most notably in MP again. Where needed, CDI implementations have been fixed long ago to support this (there were some issues initially).

Furthermore, years ago we developed an @Pooled at OmniFaces (at the time for a customer to mimic some EJB semantics in CDI), which I could ask for if it can be donated.

Kind regards,

Arjan

On Wed, Mar 17, 2021 at 4:35 PM Nathan Rauh <nathan.rauh@xxxxxxxxxx> wrote:

+1

I'd like to see all of these features go in.  My guess is that we will find there is too many for all of them to actually make it into Jakarta EE 10, but that's okay because for any that don't they can just go into the next version after that.  I suppose this is all the more reason to start sooner rather than later.  Do we need to wait for the release plan (or for any Jakarta EE 9.1 work to finish?), or can we start creating pulls against master for some of these -- especially those that are copy from other specs -- already?




From:        Reza Rahman <reza_rahman@xxxxxxxxx>
To:        cu developer discussions <cu-dev@xxxxxxxxxxx>
Date:        03/17/2021 10:30 AM
Subject:        [EXTERNAL] Re: [cu-dev] Proposed features for Concurrency 3 and Jakarta EE 10
Sent by:        "cu-dev" <cu-dev-bounces@xxxxxxxxxxx>

---

Looks good to me. It will be a very strong step forward if this can be done. It has been a long time coming.

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 Mar 17, 2021, at 11:19 AM, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:



 

Hi,

 

I’ve done some issue grooming and incorporated feedback from Jakarta EE Ambassadors and come up with this list of potential features for Jakarta EE 10/Concurrency 3.0.

3.0 Milestone (github.com)

 

This is quite a large list but some issues will be replicating and generalising some capabilities in other specs e.g. EJB spec and some work on context propagation etc. has also been done in MicroProfile I feel it is doable.

 

I also feel Jakarta Concurrency should be included in Web Profile and a Core profile if it is created so that spec specific equivalents of these concurrency capabilities could be deprecated in Jakarta EE 10 in preference for the Jakarta Concurrency equivalents, knowing that Jakarta Concurrency is available in all profiles.

 

Please reply with thoughts either on the list or on specific issues if you agree or disagree. My aim is to create a release plan by the 15^thApril deadline.

 

Thanks

 

Steve

 

_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev



_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev

_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev