[
https://issues.apache.org/jira/browse/KARAF-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403230#comment-13403230
]
Christian Schneider commented on KARAF-1572:
--------------------------------------------
You can add it to this ticket or create a new one both are fine. One question
is of course how does you locking work? As far as I know the transaction is the
way to make sure you have a relyable lock. So we have to make sure your
alternative solution works as well as this.
> Add SQL Server Support for JDBC Lock
> -------------------------------------
>
> Key: KARAF-1572
> URL: https://issues.apache.org/jira/browse/KARAF-1572
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-instance
> Affects Versions: 2.2.7
> Reporter: Claudio Corsi
> Fix For: 2.2.9, 2.3.0, 3.1.0
>
>
> The current JDBCLock implementations do not work when using Microsoft SQL
> Server since this requires that you use a CURSOR with the SELECT statement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
