[
https://issues.apache.org/jira/browse/TOMEE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392890#comment-14392890
]
Romain Manni-Bucau commented on TOMEE-1537:
-------------------------------------------
Well this is *not* a workaround, here are two points:
1) not sure why you call DataSourceFactory, this is an internal and you can
only use it at your own risks
2) definition is a serialized version of properties by design and will stay
this way while we dont completely rework this factory
creating resource from a custom API should use ConfigurationFactory and
Assembler but here again it is internals we can make evolving without any
warnings even in minors
> DataSourceFactory.create method removes the single backslash from MS SQL
> Server jdbcUrl string that contains SQL Server instance name that causes
> dataSoruce.getConnection() to throw SQLServerException.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TOMEE-1537
> URL: https://issues.apache.org/jira/browse/TOMEE-1537
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: Windows, Sql Server 2012, MS Sql Server JDBC Driver 4
> Reporter: John Pratt
> Priority: Critical
>
> If you pass in a valid connection string to the DataSourceFactory.create
> method that contains a single backslash i.e.,
> jdbcUrl=jdbc:sqlserver://IN08268\SQLEXPRESS. The DataSource factory
> implementation parses the “definition” String as java.util.Properties.
> Parsing the string as java.util.Properties removes the single backslash
> character that cause JDBC driver to fail.
> There is a workaround you could do to replace the single backslash with
> double backslash in the jdbcUrl property (but this is an invalid conection
> url for sql server).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
