|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I'm not sure if the pull request is the best way to fix this issue. the SettingsFacory and LogicalConnectionImpl seems duplicated to me. and I also see there are other places that call org.hibernate.engine.jdbc.internal.JdbcServicesImpl#getConnectionProvider directly, for example JdbcIsolationDelegate , JtaIsolationDelegate, they are all going to throw null point exception probably if multi tenancy is used.