Re: [jakartaee-platform-dev] Redefine what Priority annotation means acr

["Nathan Rauh" <nathan.rauh@xxxxxxxxxx>]

If I understood Emily's
writeup correctly, it sounds like usage is mostly consistent across all
of Interceptors, JAX-RS, and CDI processing of interceptors, which all
prioritize lower numbers first, whereas only CDI Alternatives use the opposite
prioritization (high numbers first).  In that case, we could consider
a less intrusive approach of standardizing the more prevalent usage pattern
for the existing Priority annotation and introducing a new  optional
priority attribute to CDI @Alternative (takes precedence over @Priority
when both are specified), which would then be the only part of the programming
model that we would encourage users to switch.




From:
       "BJ
Hargrave" <hargrave@xxxxxxxxxx>
To:
       jakartaee-platform-dev@xxxxxxxxxxx
Date:
       11/09/2021
08:49 AM
Subject:
       [EXTERNAL]
Re: [jakartaee-platform-dev] Redefine what Priority annotation means across
Jakarta EE specifications
Sent
by:        "jakartaee-platform-dev"
<jakartaee-platform-dev-bounces@xxxxxxxxxxx>

---

I think C makes the
most sense. I did comment on the proposed name of the annotation in the
doc.
 
Also, solution C must
state that if both the old (Priority) and new annotations are present,
the old annotation is ignored.
--

BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and OSGi Specification Project lead // mobile: +1 386 848 3788
hargrave@xxxxxxxxxx
 
 
----- Original message
-----
From: "Brian Stansberry" <brian.stansberry@xxxxxxxxxx>
Sent by: "jakartaee-platform-dev" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
To: "jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: "JakartaEE Spec Project Leadership discussions" <jakartaee-spec-project-leads@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] Redefine what Priority
annotation means across Jakarta EE specifications
Date: Tue, Nov 9, 2021 09:42
  
So, AIUI the
Solution C idea of a new annotation would result in Interceptors/CDI/JAX-RS
continuing to support @Priority in EE 10 with the EE 8/9 semantics, and
then also support the new one?
 
A solution like
that that preserves existing behavior sounds good.
  
On Tue, Nov 9, 2021
at 6:09 AM Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx>
wrote:
As promised in last
week's Jakarta EE platform call, I have created this
doc to list
the problem with the annotation of @Priority on Jakarta Annotations
specification and proposed a few solutions for further conversation. Please
take a look at the doc and comment on this thread on which solution do
you prefer. Additionally, if you have other solutions, please add it to
the doc.
 

-- 
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

-- 
Brian Stansberry 
Principal Architect,
Red Hat JBoss EAP
He/Him/His
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
 

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