[cdi-dev] [jsr366-experts] Common Annotations Maintenance Draft

Mark Paluch mpaluch at paluch.biz
Tue May 31 05:09:09 EDT 2016


+1 That idea was all the time on my mind. Removing the restriction does not hurt and enables reusability.

> Am 31.05.2016 um 08:52 schrieb Mark Struberg <struberg at yahoo.de>:
> 
> +1
> 
> It makes no sense to restrict the target for such a generic annotation.
> 
> txs and LieGrue,
> strub
> 
> 
>> Am 26.05.2016 um 09:16 schrieb Martin Kouba <mkouba at redhat.com>:
>> 
>> I wonder whether it makes sense to restrict @Priority target at all?
>> 
>> Specs/libs/frameworks might use it for methods, fields, etc.
>> 
>> Martin
>> 
>> 
>> Dne 25.5.2016 v 11:50 Antoine Sabot-Durand napsal(a):
>>> Hi Guys,
>>> 
>>> I forward below, the mail Linda sent to Java EE EG ML last week
>>> regarding MR of Commons annotations. For me it's fine but you may want
>>> to have a look.
>>> 
>>> Antoine
>>> 
>>> ---------- Forwarded message ---------
>>> From: Linda DeMichiel <linda.demichiel at oracle.com
>>> <mailto:linda.demichiel at oracle.com>>
>>> Date: jeu. 19 mai 2016 à 23:59
>>> Subject: [jsr366-experts] Common Annotations Maintenance Draft
>>> To: <jsr366-experts at javaee-spec.java.net
>>> <mailto:jsr366-experts at javaee-spec.java.net>>
>>> 
>>> 
>>> I've uploaded drafts of the Common Annotation spec + javadocs
>>> to https://java.net/projects/javaee-spec/downloads.
>>> 
>>> The functional changes are the addition of @Target(PARAMETER) to
>>> the Priority annotation as requested by the CDI expert group
>>> and making the Resource and DataSourceDefinition annotations
>>> repeatable.
>>> 
>>> I've also corrected some minor inconsistencies between this spec and
>>> the Interceptor spec on PostConstruct and PreDestroy, and replaced the
>>> example in section 2.1 referencing WebService/WebMethod, which was
>>> inconsistent with the JAX-WS and Web Services Metadata specs.
>>> 
>>> All other changes are intended as purely editorial.
>>> 
>>> If you catch anything amiss, please let me know as soon as
>>> possible, as I am planning to submit these materials to the
>>> JCP next week to initiate a Maintenance Review.
>>> 
>>> thanks,
>>> 
>>> -Linda
>>> 
>>> 
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>> 
>>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
>>> 
>> 
>> -- 
>> Martin Kouba
>> Software Engineer
>> Red Hat, Czech Republic
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>> 
>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.




More information about the cdi-dev mailing list