-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
10.0.0.Final
-
None
-
None
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.