<div dir="ltr"><div>It seems, Java SE 8 despite released in 2014 used an OLDER version of JSR 250 (1.0 or 1.1 at most) than Java EE 7, where @Priority (from 1.2) is included.</div><div><br></div><div class="gmail_extra">For consistency EE 8 will certainly keep it, but as of now, one would have to ask SE 8 to include the new version. Since EE 8 will build on SE 8 that seems like a conflict or at least redundancy if you have 2 identical annotations in the same classpath;-)</div><div class="gmail_extra"><br></div><div class="gmail_extra">So it isn't just an issue for CDI alone, somewhere before EE 8 goes final, SE 8 will have to update to 1.2 or whatever is available then, so EE 8 can simply build on top of it instead of including a newer version of the same API in a pre-Jigsaw setup where this isn't a good thing to have, especially not on a platform level;-)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Should the Spec Lead of 250 be able to update @Priority before SE 8 fixes the inconsistency, then it would solve the Problems of both CDI 2 (light) and the full EE 8 stack.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div dir="ltr"><span style="font-family:arial,sans-serif">
<p style="margin:0px;font-size:13px;border-collapse:collapse"><span style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;border-collapse:separate;font-size-adjust:none;font-stretch:normal"><span style="font-family:Helvetica"><span style="font-family:Calibri;font-size:12px"></span></span></span></p>
<div><font face="Arial"><span style="font-family:arial,sans-serif">
<p style="margin:0px;font-size:13px;border-collapse:collapse"><span lang="EN-US" style="font-family:Calibri">Werner</span></p></span><p style="margin:0px;font-size:13px;border-collapse:collapse"><br></p></font><p style="margin:0px;font-size:13px;border-collapse:collapse"><br></p></div></span></div></div><div class="gmail_extra"><br></div><div class="gmail_quote">On Tue, Oct 28, 2014 at 12:50 PM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [VOTE] Using @Priority to order events instead of adding<br>
a parameter in @Observes (John D. Ament)<br>
2. Re: cdi-dev Digest, Vol 47, Issue 13 (Werner Keil)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 28 Oct 2014 07:48:53 -0400<br>
From: "John D. Ament" <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
Subject: Re: [cdi-dev] [VOTE] Using @Priority to order events instead<br>
of adding a parameter in @Observes<br>
To: Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
Cc: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<CAOqetn9rpHpZNUV8UfK5Bn=+0S_TgZv=<a href="mailto:QN2xLW79SA25p4pP9g@mail.gmail.com">QN2xLW79SA25p4pP9g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
-1 (vote for a param in @Observes)<br>
<br>
The reason being, it sounds like there's a lot of unknowns/gaps with trying<br>
to do #1. Plus only part of 250 ships with the JVM, as the rest of it<br>
comes from the EE spec:<br>
<a href="https://javaee-spec.java.net/nonav/javadocs/javax/annotation/Priority.html" target="_blank">https://javaee-spec.java.net/nonav/javadocs/javax/annotation/Priority.html</a><br>
<br>
<br>
<br>
On Tue, Oct 28, 2014 at 4:56 AM, Antoine Sabot-Durand <<br>
<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>> wrote:<br>
<br>
> To add events ordering feature we have two choices:<br>
><br>
> 1) Use @Priority from common annotation specification (JSR-250) (vote +1)<br>
> pros:<br>
> - more consistent with other ordering mechanism we already have in CDI<br>
> (Interceptors, decorators, Alternatives)<br>
> - more Java EE consistent<br>
><br>
> cons:<br>
> - time consumed in JSR 250 MR participation (@Priority must be update to<br>
> support parameter for target)<br>
> - as @Priority is not part of Java SE, CDI light on java SE will have to<br>
> add the jsr250 jar as dependency only to have this annotation (which will<br>
> make it a little less light)<br>
><br>
> 2) Add a parameter to @Observes annotation to give order to an observer<br>
> (vote -1)<br>
> pros:<br>
> - works out of the box (we can add this property without ask for other<br>
> specs modification)<br>
> - avoid two annotations to declare an ordered observer (simpler usage)<br>
><br>
> cons:<br>
> - less Java EE spirit<br>
> - could be seen as an inconsistency with the way we order Interceptors,<br>
> Decorators and Alternatives.<br>
><br>
> ????????????????????<br>
><br>
> Who can vote? Everybody registered to this ML can vote. All votes will be<br>
> binding<br>
> How to vote? Answer this mail and vote +1 (for @Priority) 0 or -1(for<br>
> parameter in @Observes)<br>
> Vote will be closed in 72 hours<br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the<br>
> code under the Apache License, Version 2 (<br>
> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/fe500398/attachment-0001.html" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/fe500398/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 28 Oct 2014 12:50:14 +0100<br>
From: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Subject: Re: [cdi-dev] cdi-dev Digest, Vol 47, Issue 13<br>
To: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<CAAGawe2F9sw28==u28pexbMehB2V3Y=<a href="mailto:pvY1qS2YEZHoGmO%2BsFw@mail.gmail.com">pvY1qS2YEZHoGmO+sFw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Interestingly there is no @Priority in Java SE 8 see that JavaDoc:<br>
<a href="http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html" target="_blank">http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html</a><br>
<br>
Meaning we won't get that one via Java 8 anyway, and it shows, there could<br>
be flexibility to pick just the annotations you need for CDI 2 under the<br>
right circumstances, too[?]<br>
<br>
<br>
<br>
On Tue, Oct 28, 2014 at 12:43 PM, <<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a>> wrote:<br>
<br>
> Send cdi-dev mailing list submissions to<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of cdi-dev digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: [VOTE] Using @Priority to order events instead of adding<br>
> a parameter in @Observes (Werner Keil)<br>
> 2. Re: [VOTE] Using @Priority to order events instead of adding<br>
> a parameter in @Observes (Pete Muir)<br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 28 Oct 2014 11:43:31 +0000<br>
> From: Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>><br>
> Subject: Re: [cdi-dev] [VOTE] Using @Priority to order events instead<br>
> of adding a parameter in @Observes<br>
> To: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
> Cc: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> Message-ID: <<a href="mailto:A2F18F27-2750-4C0C-8CF0-BD1E50227087@redhat.com">A2F18F27-2750-4C0C-8CF0-BD1E50227087@redhat.com</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> No, it is part of the JDK - check out the packages available in your IDE,<br>
> or look at the Javadoc.<br>
> <a href="http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html" target="_blank">http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html</a><br>
> <<br>
> <a href="http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html" target="_blank">http://docs.oracle.com/javase/8/docs/api/javax/annotation/package-summary.html</a><br>
> ><br>
><br>
> We can get an MR no problem, however it is critical IMO that this update<br>
> makes it in the JDK in a timely fashion to avoid people having to use the<br>
> endorsed dir to upgrade JSR-250 (Antoine mentioned you have to add it as a<br>
> dependency, but it?s worse - you have to add it to the endorsed dir).<br>
><br>
> > On 28 Oct 2014, at 11:40, Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>> wrote:<br>
> ><br>
> > AFAIK that is not part of the JDK, thus it should make it easier to ask<br>
> them for a MR, last happened about a year ago:<br>
> <a href="https://jcp.org/en/jsr/detail?id=250" target="_blank">https://jcp.org/en/jsr/detail?id=250</a> <<a href="https://jcp.org/en/jsr/detail?id=250" target="_blank">https://jcp.org/en/jsr/detail?id=250</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Tue, Oct 28, 2014 at 12:33 PM, Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a> <mailto:<br>
> <a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>>> wrote:<br>
> > I would be +1 if we can get a commitment to update the version of<br>
> JSR-250 shipped in the JDK updated as well, otherwise -1<br>
> ><br>
> >> On 28 Oct 2014, at 10:13, Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a> <mailto:<br>
> <a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>>> wrote:<br>
> >><br>
> >> +1 for 1)<br>
> >><br>
> >> Unlike @Inject the Maven JAR for JSR-250 is a bit bigger (~20kb) but<br>
> there are existing dependencies that are not part of the JDK, most notably<br>
> JSR-330.<br>
> >><br>
> >> Not sure, if subpackages like "security" or "sql" under 250 matter at<br>
> all, if not, we could explore if the ideas for "stripping" libraries<br>
> proposed by Oracle may also work for SE/EE. This was discussed by OpenJDK<br>
> architects including Mark Reinhold with the EC. So far no real progress on<br>
> that, but till this JSR goes final or EE 8 it could work to get<br>
> dependencies a bit lighter, too.<br>
> >><br>
> >> It is likely, some annotation JSRs not just 250 need overhaul, e.g. to<br>
> finally make use of JSR-308, so an MR for 250 could be cumbersome, but<br>
> seems much easier here than e.g. bringing JSR-305 back to life;-)<br>
> >><br>
> >> Werner<br>
> >><br>
> >><br>
> >> On Tue, Oct 28, 2014 at 9:58 AM, <<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
> <mailto:<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a>>> wrote:<br>
> >> Send cdi-dev mailing list submissions to<br>
> >> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> >><br>
> >> To subscribe or unsubscribe via the World Wide Web, visit<br>
> >> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a> <<br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>><br>
> >> or, via email, send a message with subject or body 'help' to<br>
> >> <a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a> <mailto:<br>
> <a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a>><br>
> >><br>
> >> You can reach the person managing the list at<br>
> >> <a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a> <mailto:<br>
> <a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a>><br>
> >><br>
> >> When replying, please edit your Subject line so it is more specific<br>
> >> than "Re: Contents of cdi-dev digest..."<br>
> >><br>
> >><br>
> >> Today's Topics:<br>
> >><br>
> >> 1. Re: microbenchmark for CDI performance (Mohan Radhakrishnan)<br>
> >> 2. [VOTE] Using @Priority to order events instead of adding a<br>
> >> parameter in @Observes (Antoine Sabot-Durand)<br>
> >> 3. No meeting tomorrow (Antoine Sabot-Durand)<br>
> >> 4. Updated Invitation: CDI weekly meeting @ Weekly from 18:00 to<br>
> >> 19:00 on Wednesday except Wed 1 Oct 18:00, Wed 15 Oct 18:00 or<br>
> >> Wed 29 Oct 18:00 (ASD Perso) (<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a> <mailto:<br>
> <a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>>)<br>
> >><br>
> >><br>
> >> ----------------------------------------------------------------------<br>
> >><br>
> >> Message: 2<br>
> >> Date: Tue, 28 Oct 2014 09:56:14 +0100<br>
> >> From: Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a> <mailto:<br>
> <a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>>><br>
> >> Subject: [cdi-dev] [VOTE] Using @Priority to order events instead of<br>
> >> adding a parameter in @Observes<br>
> >> To: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>>><br>
> >> Message-ID: <<a href="mailto:ECAAD9B3-649C-4856-BB24-82AB9EF41763@sabot-durand.net">ECAAD9B3-649C-4856-BB24-82AB9EF41763@sabot-durand.net</a><br>
> <mailto:<a href="mailto:ECAAD9B3-649C-4856-BB24-82AB9EF41763@sabot-durand.net">ECAAD9B3-649C-4856-BB24-82AB9EF41763@sabot-durand.net</a>>><br>
> >> Content-Type: text/plain; charset=utf-8<br>
> >><br>
> >> To add events ordering feature we have two choices:<br>
> >><br>
> >> 1) Use @Priority from common annotation specification (JSR-250) (vote<br>
> +1)<br>
> >> pros:<br>
> >> - more consistent with other ordering mechanism we already have in CDI<br>
> (Interceptors, decorators, Alternatives)<br>
> >> - more Java EE consistent<br>
> >><br>
> >> cons:<br>
> >> - time consumed in JSR 250 MR participation (@Priority must be update<br>
> to support parameter for target)<br>
> >> - as @Priority is not part of Java SE, CDI light on java SE will have<br>
> to add the jsr250 jar as dependency only to have this annotation (which<br>
> will make it a little less light)<br>
> >><br>
> >> 2) Add a parameter to @Observes annotation to give order to an observer<br>
> (vote -1)<br>
> >> pros:<br>
> >> - works out of the box (we can add this property without ask for other<br>
> specs modification)<br>
> >> - avoid two annotations to declare an ordered observer (simpler usage)<br>
> >><br>
> >> cons:<br>
> >> - less Java EE spirit<br>
> >> - could be seen as an inconsistency with the way we order Interceptors,<br>
> Decorators and Alternatives.<br>
> >><br>
> >> ????????????????????<br>
> >><br>
> >> Who can vote? Everybody registered to this ML can vote. All votes will<br>
> be binding<br>
> >> How to vote? Answer this mail and vote +1 (for @Priority) 0 or -1(for<br>
> parameter in @Observes)<br>
> >> Vote will be closed in 72 hours<br>
> >><br>
> >> _______________________________________________<br>
> >> cdi-dev mailing list<br>
> >> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> >> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a> <<br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>><br>
> >><br>
> >> Note that for all code provided on this list, the provider licenses the<br>
> code under the Apache License, Version 2 (<br>
> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a> <<br>
> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>>). For all other ideas<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
> ><br>
> ><br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/7a4d9ef6/attachment.html" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/7a4d9ef6/attachment.html</a><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the<br>
> code under the Apache License, Version 2 (<br>
> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
><br>
> End of cdi-dev Digest, Vol 47, Issue 13<br>
> ***************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/ee9da88a/attachment.html" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/ee9da88a/attachment.html</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: image/gif<br>
Size: 186 bytes<br>
Desc: not available<br>
Url : <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/ee9da88a/attachment.gif" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20141028/ee9da88a/attachment.gif</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 47, Issue 14<br>
***************************************<br>
</blockquote></div><div class="gmail_extra"><br></div></div>