]
Chao Wang commented on WFLY-3538:
---------------------------------
With another local experiment, I can execute followings commands within CLI to remove the
default datasource binding. And no ERROR pops up during deployment.
{noformat}
# /subsystem=datasources/data-source=ExampleDS:remove()
# /subsystem=ee/service=default-bindings:write-attribute(name=datasource,value=undefined)
# deploy xxx.war
{noformat}
Please let me know if this satisfies your requirement.
Application does not deploy because DefaultDataSource is missing
----------------------------------------------------------------
Key: WFLY-3538
URL:
https://issues.jboss.org/browse/WFLY-3538
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 8.1.0.Final
Environment: Debian linux 7.5, openjdk 7u55-2.4.7-1~deb7u1, Wildfly 8.1.0.Final
Reporter: Peter Van Biesen
Assignee: Chao Wang
On our servers, the ExampleDs is removed from the config. In 7.2.0, this poses no
problem, but in the 8.1.0.Final, when we deploy an application, the default datasource
needs to be available, even if the application does not use a datasource. The error :
{code}
failure description: {"JBAS014771: Services with missing/unavailable
dependencies" =>
["jboss.naming.context.java.module.jolokia.jolokia.DefaultDataSource is missing
[jboss.naming.context.java.jboss.datasources.ExampleDS]"]}
{code}
The example above is for the deployment of the jolokia war.
To reproduce :
* remove ExampleDS
* deploy any application