-
1. Re: WildFly 8 RC1 DefaultDataSource doesn't work
smarlow Feb 4, 2014 9:02 AM (in response to guidogranobles)Can you show us the entire deployment error for the "Incompatible conflicting binding" error (including the exception call stack)?
Can you also show us a code example that experiences this problem.
-
2. Re: WildFly 8 RC1 DefaultDataSource doesn't work
jameslivingston Feb 7, 2014 7:40 AM (in response to guidogranobles)Guido Granobles wrote:
But if I change my datasource like this java:comp/DefaultDataSource I got an error telling me that datasources in JBoss must start with java:/jboss/. So I'm stuck with this problem.
You can't globally bind the datasource to java:comp, since that's the EE component namespace - if that's what you were trying to do.
As Scott said, the error stack trace and some details would be helpful for the original problem.
-
3. Re: WildFly 8 RC1 DefaultDataSource doesn't work
jason.greene Feb 10, 2014 1:37 PM (in response to guidogranobles)
The default datasource is an alias to a normal jboss configured datasource. Look at the ee subsystem in your standalone.xml, you can just point it to the datasource of your choice. -
4. Re: WildFly 8 RC1 DefaultDataSource doesn't work
jeslinedias Apr 14, 2017 2:13 PM (in response to jason.greene)Hey Jason,
Can you be a little detailed on what you are referring to in the ee subsystem ? I am using EAP 7 and my ee subsystem looks like this.
<subsystem xmlns="urn:jboss:domain:ee:4.0">
<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
<concurrent>
<context-services>
<context-service name="default" jndi-name="java:jboss/ee/concurrency/context/default" use-transaction-setup-provider="true"/>
</context-services>
<managed-thread-factories>
<managed-thread-factory name="default" jndi-name="java:jboss/ee/concurrency/factory/default" context-service="default"/>
</managed-thread-factories>
<managed-executor-services>
<managed-executor-service name="default" jndi-name="java:jboss/ee/concurrency/executor/default" context-service="default" hung-task-threshold="60000" keepalive-time="5000"/>
</managed-executor-services>
<managed-scheduled-executor-services>
<managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/>
</managed-scheduled-executor-services>
</concurrent>
<default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="java:jboss/datasources/ExampleDS" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>
</subsystem>
What should i be changing in this to get this going ?
-
5. Re: WildFly 8 RC1 DefaultDataSource doesn't work
ctomc Apr 14, 2017 3:45 PM (in response to jeslinedias)Jesline Dias Jevigeorge wrote:
Hey Jason,
Can you be a little detailed on what you are referring to in the ee subsystem ? I am using EAP 7 and my ee subsystem looks like this.
<subsystem xmlns="urn:jboss:domain:ee:4.0">
....<default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="java:jboss/datasources/ExampleDS" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>
....
</subsystem>
What should i be changing in this to get this going ?