[arquillian-issues] [JBoss JIRA] Commented: (ARQ-201) Primitive fields annotated with @Resource are not assigned
[
https://jira.jboss.org/browse/ARQ-201?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-201:
-----------------------------------
The reason for checking for null is to see if another Enricher has all ready set the
field. E.g. The CDI enricher can handle @Resource better then we can.
So for primitives, which is the lesser evil?
- Always try to lookup primitives, since we can't really determine if they have been
set or not?
- Assume a primitive with it's default value (0) is not set, even tho that could be
it's real value?
- Fail/Report error/warning, primitives not supported. Who binds/needs primitives anyway?
:)
Primitive fields annotated with @Resource are not assigned
----------------------------------------------------------
Key: ARQ-201
URL: https://jira.jboss.org/browse/ARQ-201
Project: Arquillian
Issue Type: Bug
Components: Runtime Enricher SPI
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Priority: Minor
Fix For: 1.0.0.Alpha3
Fields which are not null are skipped when performing @Resource injections. However,
primitive fields are never null and therefore injections do not occur on those fields.
Example:
@Resource(name = "port") int port;
--
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