[
https://jira.jboss.org/browse/WELD-473?page=com.atlassian.jira.plugin.sys...
]
Pete Muir closed WELD-473.
--------------------------
Resolution: Won't Fix
Unfortunately this is not fixable.
1) The may from the CDI spec comes from the fact you may enhance the annotation via the
CDI SPI (BeforeBeanDiscovery#addQualifier)
2) The @Qualifer annotation comes from JSR-330, which imposes a minimal set of
requirements (such as the @Retention), and allows an injector (in this case JSR-299) to
restrict the @Target further. As this javadoc comes from an API out of our control, we
can't fix it.
required meta-annotations for a qualifier specified differently in
spec and API
-------------------------------------------------------------------------------
Key: WELD-473
URL:
https://jira.jboss.org/browse/WELD-473
Project: Weld
Issue Type: Bug
Components: CDI API
Affects Versions: 1.0.1.Final
Environment: n/a
Reporter: Wolfgang Frech
Assignee: Pete Muir
Fix For: 1.1.0.BETA1
The specification and the API documentation differ on the required and optional
meta-annotations of a qualfiier.
JSR-299, 2.3.2 Defining new qualfier type specifies
@Target(METHOD, FIELD, PARAMETER, TYPE} ("is")
@Retention(RUNTIME) ("is")
@Qualifier, but only optional ("may")
API-Doc of Qualifier specifies
@Qualifier
@Retention(RUNTIME)
@Documented (optional, typical)
@Target optional, but various element types as targets possible
Both agree on Retention only.
As a third source I might have a look at the code and the implemented validity check. I
have not so far.
I am a bit fussy about this because a missing @Target of my first custom scope messed up
the proxying.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira