Issue 3522: CosConsurrencyControl service bug or not? (issues)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: I develop CosConcurrencyControl service for JacORB, but I don't
understud from specification how client can destroy LockSet.
When I create Object which allow concurrency access, I create LockSet.
When I destroy this Object I must destroy LockSet, because it's garbage,
bu no way for this does not exists.

As solution of this problem,  I add in CosConcurrencyControl.idl  next
changes:
exception LockExists{};

and method
void destroy raises (LockExists);

in interface LockSet.

As I undestand this changes is wrong, but have you idea about desigion
this problem.

Resolution: 
Revised Text: 
Actions taken:
March 28, 2000: received issue
Discussion: 

End of Annotations:=====
Date: Tue, 28 Mar 2000 14:25:51 +0300
From: Viacheslav N Tararin <taras@deka.kp.km.ua>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: omg.org!vendors@deka.kp.km.ua,
        Gerald Brose <inf.fu-berlin.de!brose@deka.kp.km.ua>
Subject: CosConsurrencyControl service bug or not?
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: ~!m!!L$Qe9%-\!!L2@e9

Hi.

I develop CosConcurrencyControl service for JacORB, but I don't
understud from specification how client can destroy LockSet.
When I create Object which allow concurrency access, I create LockSet.
When I destroy this Object I must destroy LockSet, because it's
garbage,
bu no way for this does not exists.

As solution of this problem,  I add in CosConcurrencyControl.idl  next
changes:
exception LockExists{};

and method
void destroy raises (LockExists);

in interface LockSet.

As I undestand this changes is wrong, but have you idea about desigion
this problem.

Regards,
Viacheslav Tararin.