Hi,

Hi Evgeny,

I am not sure if I follow your question. When you make the embedding relationship ContainerHasComponent, a relationship is created (not a DomainProperty) for that relationship. Since FileComponent inherits from Components, you should be able to use either DomainClasses as targets of the relationship (as long as you also make a Toolbox element corresponding to the FileComponent). There is no need to create an extra relationship for your derived classes.

Hope this helps.

Bhavin B

DSL Tools - SDET

Hi Bhavin,

Actually, I just want to have an aditional property in a generated class wich represent a Container domain class. The reason is to have a filtered by the type list of components. I mean, for example, when I use T4 templates, I have an instance of my model element and I can obtain the list of all components by this way - this.MyModel.Container.Components. But if I need only a FileComponent component I have to get all of them and then filter them in a code, instead of having a new property like this this.MyModel.Container.FileComponents.

I hope now I make it clear.

Evgeny

Hi Evgeny,

We use derived relationships to implement this type of functionality - unfortunately, they don't really work in the shipping CTPs in the DslDesigner - they will however work correctly in the V1 code.

What you'll do is to make a second relationship between Container and FileComponent "ContainerHasFileComponents".

You'll then set the base class of "ContainerhasFileComponents" to be "ContainerHasComponents"

This should give you exactly the behaviour you desire. You'll probably want to set the "IsPropertyGenerator" flag to false on the target roleplayer of the derived relationship as the base relationship will generate you a "Container" property fot the parent relationship.

The one thing you need to be aware of is that it is still possible to create a link of the base type between a Container and a FileComponent as those types are fully type compatible with the both DomainRelationships and the base class is concrete. If you can make Component and FileComponent siblings both derived from an abstract base DomainClass then you can mirror that with an abstract relationship as the aggregate collection and two concrete relationships.