Hello,
From Infrastructure 2.1.1 (
http://www.omg.org/cgi-bin/doc?formal/07-02-06 page 43 ) : "An Element is a constituent of a model. Element is an abstract metaclass with no superclass. It is used as the common superclass for all metaclasses in the infrastructure library."
Hope it helps you in your decision. Bogdan On 3/29/07, Bob Tarling <[EMAIL PROTECTED]> wrote:
How about isAUMLElement - I think Element is a UML2 class and so it's meaning will be futureproof. Bob. On 29/03/07, Michiel van der Wulp <[EMAIL PROTECTED]> wrote: > Hi All, > > Recently, I realised that in MDR not all UML objects are a ModelElement. > These are ElementOwnership (does not exist in MDR), ElementResidence, > ElementImport, TemplateParameter, TemplateArgument, and the data types > Multiplicity, MultiplicityRange, Expression. > This may be incorrect (see 4.5.2.27), but that is another discussion. > > In many places in ArgoUML's code, the function > Model.getFacade().isAModelElement(x) is used to determine if we are dealing > with a UML object, and not with e.g. a Fig, null, or a Diagram. > > This is obviously wrong. Please try not to do this! > > > One example is UMLModelElementListModel2.setTarget(), which makes it hard to > create a proppanel for e.g. a ElementResidence. > > To ease solving this, can we create a function with the name "isAUMLObject" > or "isAUMLClass" in the model subsystem? The latter would be similar to the > existing "getUMLClassName". > Or is there another idea? > > Regards, > Michiel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
