Issue 6525: two classes "NamedElement (uml2-rtf)
Source: Pivot Point (Mr. Cris Kobryn, )
Nature: Uncategorized Issue
Severity: 
Summary: Secondly, there are two classes "NamedElement" holding un-redefined 
attribute "name", one is in the 
package "InfrastructureLibrary.Core.Basic", and the other is in the 
package "InfrastructureLibrary.Core.Abstractions.Namespaces". The 
problem is that there are a lot of classes directly or indirectly 
inheriting both of them e.g. class "InstanceSpecification" in package 
uml.classes.kernel, and it causes problem of duplicated parameters in 
class creation in the generated JMI interfaces. e.g. 
"
public InstanceSpecification createInstanceSpecification
(java.lang.String name, 
infrastructurelibrary.core.abstractions.visibilities.VisibilityKind 
visibility, java.lang.String name, java.util.Collection classifier); 
"
Similiar cases happen to attribute "type", "isAbstract" etc.

Resolution: 
Revised Text: 
Actions taken:
November 7, 2003: received issue
February 18, 2005: moved from infrastructure
August 23, 2006: closed issue
Discussion: 
The submitter seems to be unfamiliar with the rules for redefinition and package merge,
which resolve such issues in general. In this particular case, due to the fact that
Abstractions and Basic have been de-coupled in the FTF work, the two are completely
distinct elements and are not intended to be used together. If someone does decide to use
them together, however, package merge would resolve any contention. See also the
resolution to issue 6003 and 6002.
Disposition: Closed, no change
End of Annotations:=====
-Return: cris@ieee.org 
Date: Sat, 08 Nov 2003 07:36:45 -0000 
From: "Cris Kobryn" <cris@ieee.org> 
To: juergen@omg.org, issues@omg.org, cris.kobryn@telelogic.com 
Subject: Fwd:  bugs in UML 2.0 specification 
User-Agent: eGroups-EW/0.82 
X-Mailer: Yahoo Groups Message Poster 
X-Originating-IP: 68.71.8.84 


--- In u2p-info@yahoogroups.com, "Fu,Bin" <fubin@g...> wrote:
Hi,


I am doing a job to convert U2P-UML-Infra-v2-XMI-030303.xmi 
(Specificaiton of UML 2.0 described by MOF 2.0 and XMI 2.0) into a 
format of XMI 1.2 and MOF 1.4, so that it can be acceptable by 
Metadata Repository (MDR).


Secondly, there are two classes "NamedElement" holding un-redefined 
attribute "name", one is in the 
package "InfrastructureLibrary.Core.Basic", and the other is in the 
package "InfrastructureLibrary.Core.Abstractions.Namespaces". The 
problem is that there are a lot of classes directly or indirectly 
inheriting both of them e.g. class "InstanceSpecification" in package 
uml.classes.kernel, and it causes problem of duplicated parameters in 
class creation in the generated JMI interfaces. e.g. 
"
public InstanceSpecification createInstanceSpecification
(java.lang.String name, 
infrastructurelibrary.core.abstractions.visibilities.VisibilityKind 
visibility, java.lang.String name, java.util.Collection classifier); 
"
Similiar cases happen to attribute "type", "isAbstract" etc.



Above problems are some of what I found in UML 2.0, hope someone can 
tell me the answer. 


Thanks in advance!



Fu, Bin
--- End forwarded message