Issue 4222: Behavior of Lockable operations is not defined (pdm-rtf)
Source: NIST (Mr. Edward J. Barkmeyer, edbark(at)nist.gov)
Nature: Uncategorized Issue
Severity: 
Summary: Source: PDME-RTF, derived from issue 2485

Summary:
In section 3.3.8, the following Note appears: "Note ­ It is up to the inheriting classes to include the locking or checks for
locks on dependent objects. For example, it is up to the Document classes to define what happens to DocumentRevisions when the
Document object is locked."
But in fact, nothing in DocumentManagement defines this, nor does anything in ProductStructure define the effects of locking on
PartRevisions, nor does anything in ManufacturingImplementation define the effects of locking on ProcessRevisions, etc.  The PDM
Enablers should define the common interoperable locking behaviors on each class that inherits from Lockable, and where necessary
at least say that locking behavior is implementation-defined.

Resolution: 
Revised Text: 
Actions taken:
March 14, 2001: received issue
Discussion: 

End of Annotations:=====
Date: Wed, 14 Mar 2001 10:18:31 -0500
From: Ed Barkmeyer <edbark@nist.gov>
Reply-To: edbark@cme.nist.gov
Organization: NIST
X-Sender: "Ed Barkmeyer" <edbark@mailhost.cme.nist.gov>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (WinNT; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: issues@omg.org
CC: PDM RTF <pdm-rtf@omg.org>, JPDM <jpdm.team@mscsoftware.com>
Subject: 2 more PDM Enablers issues
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1
X-UIDL: F7;!!"[S!!PX/!!1:/e9

Issue 1

Title: Behavior of Lockable operations is not defined

Source: PDME-RTF, derived from issue 2485

Summary:
In section 3.3.8, the following Note appears: "Note - It is up to the
inheriting classes to include the locking or checks for
locks on dependent objects. For example, it is up to the Document
classes to define what happens to DocumentRevisions when the
Document object is locked."
But in fact, nothing in DocumentManagement defines this, nor does
anything in ProductStructure define the effects of locking on
PartRevisions, nor does anything in ManufacturingImplementation define
the effects of locking on ProcessRevisions, etc.  The PDM
Enablers should define the common interoperable locking behaviors on
each class that inherits from Lockable, and where necessary
at least say that locking behavior is implementation-defined