-
Bug
-
Resolution: Done
-
Major
-
7.3.3.GA
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
-
-
EAP 7.2+ is creating a dependency on the DefaultDataSource when it should not.
If the default datasource is removed from the ee subsystem and an application is deployed with a class that has @Resource specifying a name to inject which is not linked to the default datasource, it should NOT fail with a missing dependency.
This was found with a Spring application, where Spring configuration is defining java:comp/env/dataSource to link to the real datasource. In EAP 7.1 the application deployed with no issue, in EAP 7.2+ JBoss is failing the deployment due to the datasource=... being removed from the default bindings in the ee subsystem.
@Resource(name = "dataSource") private DataSource dataSource;
18:08:15,547 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "reproducer2.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.reproducer2.reproducer2.DefaultDataSource"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.reproducer2.reproducer2.env.non-existant is missing [jboss.naming.context.java.module.reproducer2.reproducer2.DefaultDataSource]"] }
- is blocked by
-
JBEAP-20652 (7.3.z) Add a new Phase ID STRUCTURE_EE_DEFAULT_BINDINGS_CONFIG
- Closed
- is cloned by
-
WFLY-14025 Unable to remove the default datasource binding from the ee subsystem
- Closed