Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 16 Aug 2012 01:00:56 +1100 (NCT)
From: "Claudio Corsi (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <1758637293.13593.1345039256853.JavaMail.jiratomcat@arcas>
In-Reply-To: <1370305832.40872.1340308362594.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Comment Edited] (KARAF-1572) Add SQL Server Support for
 JDBC Lock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-1572?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1343=
5126#comment-13435126 ]=20

Claudio Corsi edited comment on KARAF-1572 at 8/16/12 1:00 AM:
---------------------------------------------------------------

JB, that's fair enough moving this to the next release since the current on=
e is at its final stage.

As I mentioned to Jamie, I only have a small period in which I can test thi=
s against an SQL Server.  If you do get a chance to add this feature to one=
 of the branches or trunk and it is ready for testing.  I can take some tim=
e to set up a test using SQL Server as the jdbc lock.
               =20
      was (Author: ccorsi):
    JB, that fair enough moving this to the next release since the current =
one is at its final stage.

As I mentioned to Jamie, I only have small period in which I can test this =
against an SQL Server.  If you  do get a chance to add this feature to one =
of the branches or trunk and it is ready for testing.  I can take some time=
 to set up a test using SQL Server as the jdbc lock.
                 =20
> Add SQL Server Support for JDBC Lock=20
> -------------------------------------
>
>                 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
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: 2.2.10, 2.3.1, 3.1.0
>
>         Attachments: GenericJDBCLock.patch, GenericJDBCLock.patch
>
>
> 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira