Re: [jakartaee-platform-dev] [cdi-dev] [interceptors-dev] [jaxrs-dev] Re

[Reza Rahman <reza_rahman@xxxxxxxxx>]

I voted to do nothing. I am glad a few other folks think so too. I don’t think this is an important enough issue to invest too much energy into.

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.

 

---

From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Romain Manni-Bucau <rmannibucau@xxxxxxxxx>
Sent: Tuesday, January 11, 2022 7:32 AM
To: jakartaee-platform developer discussions
Cc: interceptors developer discussions; jaxrs developer discussions; cdi developer discussions
Subject: Re: [jakartaee-platform-dev] [cdi-dev] [interceptors-dev] [jaxrs-dev] Redefine what Priority annotation means across Jakarta EE specifications

 

Well since it is kind of fifty-fifty - even if a few more votes are casted it will not change the balance - I'm not sure it can be used to decide if @Priority must be created in commons but i'd like to ask yourself what would be such an annotation since the existing priorities don't have the same meaning nor semantic by design so using the same annotation for different meaning will be misleading (at least CDI shows it well with interceptors/decorators/observers) so, IMHO, it is 100% about using the existing ones and well defining the meaning in the owning specs since an order is always relative to its definition and sharing annotations will create ambiguous cases (between jaxrs and cdi for example, 3 priority annotations can be needed - one for the observer one for the jaxrs chain).

Romain Manni-Bucau
@rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book

Le mar. 11 janv. 2022 à 12:47, Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> a écrit :

Thank you all for casting your votes on this discussion! The result for @Priority is back. 60 responses were received. You can see the detailed results here.

In summary, the top options are:

Do nothing: 22.4%

Define a new annotation such as @Ranking (highest number means high priority): 22.4%

I think this survey result can influence the design for the new Jakarta Commons to define a new API that supersedes @Priority annotation.

Thanks,

Emily

On Tue, Nov 23, 2021 at 3:30 PM Matej Novotny <manovotn@xxxxxxxxxx> wrote:

Hello

Is there a way to see the current poll status?

Having cast my vote, I still couldn't find that option anywhere and I'd be curious to see what people think (and how many of them think anything at all :)).

Matej

On Sat, Nov 20, 2021 at 11:07 AM Emily Jiang <emijiang6@xxxxxxxxxxxxxx> wrote:

Thank you Reza! Very much appreciated!

Thanks 

Emily 

On 19 Nov 2021, at 23:39, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:



Well done Emily. I’ll help get the word out.

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.

 

---

From: jaxrs-dev <jaxrs-dev-bounces@xxxxxxxxxxx> on behalf of Emily Jiang <emijiang6@xxxxxxxxxxxxxx>
Sent: Friday, November 19, 2021 6:05 PM
To: jakartaee-platform developer discussions; cdi developer discussions; jaxrs developer discussions; interceptors developer discussions
Subject: Re: [jaxrs-dev] [jakartaee-platform-dev] Redefine what Priority annotation means across Jakarta EE specifications

 

Further to the conversation regarding the inconsistent usage of the Jakarta @Priority annotation, I created a survey for you to cast your vote on whether or how to proceed with the current @Priority annotation. For more information regarding this conversation, please read this proposal Please cast your votes here before 3rd December.

Thanks

Emily

On Tue, Nov 16, 2021 at 2:49 PM Emily Jiang <emijiang6@xxxxxxxxxxxxxx> wrote:

Thank you all for sharing your thoughts here! I think the next step is to vote on the solutions documented on this doc. I'll start a new thread soon.

Thanks

Emily

On Thu, Nov 11, 2021 at 7:45 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

> On Nov 9, 2021, at 11:24 AM, Mark Struberg <struberg@xxxxxxxxxx> wrote:
>
> First of all, the @Priority annotation was introduced by the CDI team. As is the specific part of the interceptors spec. Both originally have been part of CDI when spec still was called "Web Beans"...


The EJB 3.0 expert group was the first to add interceptors and still owned the spec when WebBeans came later and @Priority was added in Interceptors 12.

 - https://jcp.org/en/jsr/detail?id=318


-David

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

--

Thanks
Emily

--

Thanks
Emily

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

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

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

--

Thanks
Emily

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