Issue 7628: definition of the stereotype CORBAPrimaryKey (uml-ccm-ftf)
Source: Fraunhofer FOKUS (Mr. Tom Ritter, tom.ritter(at)fokus.fraunhofer.de)
Nature: Revision
Severity: Significant
Summary: The definition of the stereotype CORBAPrimaryKey makes too strong restrictions. The CORBA Component Model defines a primary key as an ordinary valuetype, which is derived from Components::PrimaryKeyBase. Using the stereotype PrimaryKey would prevent me from using this valuetype in other parts of my application as a plain valuetype (e.g operation parameter). Suggestion: Remove stereotyp CORBAPrimaryKey. Use stereotype CORBAValueDef instead and refomulate the constraints accordingly. (e.g. inheritance)

Resolution: 
Revised Text: 
Actions taken:
August 13, 2004: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org 
Date: 13 Aug 2004 11:05:41 -0400 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Tom Ritter
Company: Fraunhofer FOKUS
mailFrom: ritter@fokus.fraunhofer.de
Notification: Yes
Specification: UML Profile for CCM 
Section: 8.1.2
FormalNumber: ptc/03-12-01
Version: draft adopted specification
RevisionDate: December 2003
Page: 12
Nature: Revision
Severity: Significant
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.0.2) Gecko/20030208 Netscape/7.02
Description
The definition of the stereotype CORBAPrimaryKey makes too strong restrictions. The CORBA Component Model defines a primary key as an ordinary valuetype, which is derived from Components::PrimaryKeyBase. Using the stereotype PrimaryKey would prevent me from using this valuetype in other parts of my application as a plain valuetype (e.g operation parameter). Suggestion: Remove stereotyp CORBAPrimaryKey. Use stereotype CORBAValueDef instead and refomulate the constraints accordingly. (e.g. inheritance)