[
https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin....
]
Mark S edited comment on WFLY-7018 at 9/7/16 12:57 PM:
-------------------------------------------------------
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the
preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via
{{<connection-property name="url">}} instead of
{{<connection-url>}}, though I got exceptions unless both values where present (Like
in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question 1:* It sounds like Wildfly DataSources will be configured differently in
future, with different cli commands. Is this correct?
*Question 2:* Is there a better work-around than the above example, so that I can get a
Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question 3:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration
({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ...
--></subsystem>}}) that would work?
*Question 4:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration
that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource
Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration
|http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
was (Author: marks1900):
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the
preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via
{{<connection-property name="url">}} instead of
{{<connection-url>}}, though I got exceptions unless both values where present (Like
in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question 1:* In your recent comments, it sounds like Wildfly DataSources will be
configured differently in future, with different cli commands. Is this correct?
*Question 2:* Is there a better work-around than the above example, so that I can get a
Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question 3:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration
({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ...
--></subsystem>}}) that would work?
*Question 4:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration
that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource
Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration
|http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
-------------------------------------------------------------------
Key: WFLY-7018
URL:
https://issues.jboss.org/browse/WFLY-7018
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 10.1.0.Final
Reporter: Mark S
Assignee: Lin Gao
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for
Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
The stacktrace points to here:
*
https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
*
https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property
name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS"
pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property
name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker
class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter
class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)