[
https://issues.jboss.org/browse/WFLY-6157?page=com.atlassian.jira.plugin....
]
ehsavoie Hugonnet edited comment on WFLY-6157 at 2/12/16 9:25 AM:
------------------------------------------------------------------
Ok, the problem comes when you have datasource-class defined in your driver.
If a datasource-class is defined then it takes precedence to create the datasource and as
such it can only use connection-properties.
Since there is not a single connection-url property for all drivers, you have to use
connection-properties if you adre defining the datasource-class.
was (Author: ehugonnet):
Ok, the problem comes when you have datasource-class defined in your driver.
This seems to be an ironjacamar issue.
Connection URL ignored for SQL Server datasource
------------------------------------------------
Key: WFLY-6157
URL:
https://issues.jboss.org/browse/WFLY-6157
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Rich DiCroce
Assignee: Jason Greene
The connection-url for a datasource is being ignored (or more likely, getting lost
somewhere) when using WildFly with the Microsoft SQL Server JDBC driver. No matter what I
specify as the connection-url (even something obviously invalid like "foobar"),
the driver always ends up using the defaults that are baked into it.
The same driver worked fine on WildFly 10 CR2 (and many earlier versions), so some change
between then and 10 Final has caused a regression.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)