[jboss-jira] [JBoss JIRA] (WFLY-9235) @Resource injection does not fail in a servlet when the resource is missing

Stuart Douglas (JIRA) issues at jboss.org
Thu Aug 17 19:55:00 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved WFLY-9235.
----------------------------------
    Resolution: Rejected


This is allowed for simple env entries:

EE.5.4.1.3

....
It’s often convenient to declare a field or method as an injection target, but
specify a default value in the code, as illustrated in the following example.
// The maximum number of tax exemptions, configured by the Deployer.
@Resource int maxExemptions = 4; // defaults to 4
To support this case, the container must only inject a value for this resource if
the deployer has specified a value to override the default value. 

.....

> @Resource injection does not fail in a servlet when the resource is missing
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-9235
>                 URL: https://issues.jboss.org/browse/WFLY-9235
>             Project: WildFly
>          Issue Type: Bug
>          Components: Naming, Web (Undertow)
>            Reporter: Stephen Coy
>            Assignee: Stuart Douglas
>         Attachments: web45709634.jira.zip
>
>
> The attached web application builds, deploys and runs perfectly.
> However, if you remove one of the <env-entry> elements from the web.xml it will still deploy and run.
> The associated injection point is left as null instead of having the deployment fail as required by the Java EE 7 Spec in "EE.5.2.5 Annotations and Injection", where it states:
> {quote} If the container fails to find a resource needed for injection, initialization of the class must fail, and the class must not be put into service.{quote}
> Also see StackOverflow question https://stackoverflow.com/questions/45716813/glassfish-wildfly-not-failing-if-resource-cannot-be-resolved



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jboss-jira mailing list