Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » Should ValueSpecification be really a TypedElement?
Should ValueSpecification be really a TypedElement? [message #626758] Thu, 03 July 2008 12:42
Timothy Marc is currently offline Timothy MarcFriend
Messages: 547
Registered: July 2009
Senior Member
Hi all,

after studying the values and instances concepts of the UML2 superstructure,
i was wondering that a ValueSpecification is also inhereting TypedElement.
What's the main reason for this? In the case of being a
LiteralSpecification, its type is directly combined with the value argument.
In the case of beeing a InstanceValue, the instance references a
InstanceSpecification, that points to a concrete classifier.
IMHO, there is no sense in defining the ValueSpecification as a
TypedElement, or is it for the enhancing mechanism of the metamodel?

Hope, this question isn't too silly.

-- Timothy
Previous Topic:EditDomains and EAnnotation.getDetails() returns java.lang.ArrayStoreException?
Next Topic:Should ValueSpecification be really a TypedElement?
Goto Forum:

Current Time: Fri Aug 19 11:33:20 GMT 2022

Powered by FUDForum. Page generated in 0.03358 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top