missing metaclasses

[dse]

Hello! It is said that EA fully supports UML 2.0 Specification. Thow, there are many metaclasses from UML 2.0 that are not predefined in EA. I will give some examples:
-StructuredClassifier, Property, Behavior, CallOperationAction, SendObjectAction, Property, ValueSpecification, Namespace, LiteralSpecification, TimeTrigger, Message, AcceptEventAction, CallOperationAction, ReadStructuralFeatureAction, WriteStructuralFeatureAction, and the list goes on.
The problem is that I really nead those metaclasses for realizing a profile using Enterprise Architect. What should I do? If I simply choose  a Class metaclass and then change the name in the desired one it works at a first glance. Thow the problem is deeper. I want that the components from my profile to respect the given notations.
So I really nead to know if is there any posibility to introduce the above metaclasses in the EA so that they would respect the notation from the UML 2.0 specification.
Could I hardcode this somehow?

Thanks!

[KP]

Some of those are abstract metaclasses, so you can't create instances of them in EA. That includes StructuredClassifier, Behavior, ValueSpecification, Namespace, LiteralSpecification. In your profile, you would need to extend each concrete child-metaclass. One day we may make this automatic, but it's over the horizon at the moment.

Property includes attributes and tagged values, and you can certainly create those in a profile.

The various Actions are all available in profiles. Extend the Action metaclass and set the value of the "kind" attribute.

Message should be stereotype-able, so we need to do something about that one.

[dse]

For my profile I need to define a couple of stereotypes that extends, for example, StructuredClassifier.What exactly should I do in this case? I need that those stereotypes to inherit the features and notation for StructuredClassifier. What did you mean by "In your profile, you would nned to extend each concrete child-metaclass?". Can you be more explicit please? What exactly should I do to define a stereotype which extends one of the abstract metaclasses that I mentioned before. I need to realize my profile conforming to a specification.

It is the same problem with the Property metaclass. I need to define a new stereotype which extends the Property metaclass.

When I add a new metaclass in the diagram there is a list of options for the metaclasses that are available in the tool. Many of the metaclsses that I need to extend are missing.

What is to do in this case?

I need that my profile to respect entirely the specification that is provided to me.

Mabe I miss something. Please help!

Thanks!  

[KP]

Elements that are StructuredClassifiers are classes, collaborations, components and nodes. I think that's the full list, but I would have to check the UML 2.0 specification to be sure. StructuredClassifier is abstract, meaning you can't create an instance of one. That's a UML thing, not a problem with EA. You can only create one of its children (class, component, node or collaboration). Unfortunately, EA doesn't allow you at present to define stereotypes for StructuredClassifier and have them apply to class, component etc. That is a feature that we will certainly consider in the future, but it's some way away for now. For now, you will need to extend class, component, node and collaboration individually.

For the definitive answers: UML 2.0 Superstructure is available at http://www.uml.org/