Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

I logged this as a bug due to the fact we certify with the Oracle JDBC driver.
It could be argued this is an RFE.

I can see two solutions.

1. Limited to datasource and xa-datasource:
org.jboss.as.connector.subsystems.datasources.DsParser.java
-> schema change so a list of values can be assigned to a single xa-property, in JCA support a call to setXXX(java.util.Properties)

2. a universal fix to the ModelNode class to allow java.util.Properties

Show
I logged this as a bug due to the fact we certify with the Oracle JDBC driver. It could be argued this is an RFE. I can see two solutions. 1. Limited to datasource and xa-datasource: org.jboss.as.connector.subsystems.datasources.DsParser.java -> schema change so a list of values can be assigned to a single xa-property, in JCA support a call to setXXX(java.util.Properties) 2. a universal fix to the ModelNode class to allow java.util.Properties

The oracle JDBC driver had a method:
setConnectionProperties(java.util.Properties value)

which is needed to set several connection properties for datasources.
Most (all?) of these connection properties do not have individual setters.

WildFly does not support setting a "Properties" value for "datasource-property"