[
https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin...
]
Lin Gao commented on JBJCA-1320:
--------------------------------
Or you can specify the {{<connection-property>}} in the {{datasource}} element:
{code:xml}
<datasource jndi-name="java:jboss/datasources/MySqlDS"
pool-name="MySqlDS">
<connection-property
name="url">jdbc:mysql://localhost:3306/mydb</connection-property>
<driver>com.mysql</driver>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<pool>
<min-pool-size>10</min-pool-size>
<max-pool-size>100</max-pool-size>
<prefill>true</prefill>
</pool>
<security>
<user-name>root</user-name>
<password></password>
</security>
<statement>
<prepared-statement-cache-size>32</prepared-statement-cache-size>
<share-prepared-statements/>
</statement>
</datasource>
{code}
to make it work
Unable to create JDBC local datasource without properties on JBoss
EAP 7
------------------------------------------------------------------------
Key: JBJCA-1320
URL:
https://issues.jboss.org/browse/JBJCA-1320
Project: IronJacamar
Issue Type: Bug
Components: JDBC
Affects Versions: WildFly/IronJacamar 1.3.3.Final
Environment: JBoss EAP 7.0.0
Reporter: ted won
Assignee: ted won
Priority: Minor
Attachments: com.msql.tar.gz
It should display warning message than throwing error as
[
WFLY-6198|https://issues.jboss.org/browse/WFLY-6198].
It's failed with error "IJ031103: At least one connection property must be
defined for datasource-class" when it's doing migration from JBoss EAP 6 /
WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in
JBoss EAP 7.
In case of MySQL datasource classes it's possible to use datasource-class and create
non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)