<containerConfiguration xmi:id="_tgfvMJgmEeSbPLBxcMMcNg"> <eContainmentFeatures href="http://www.eclipse.org/uml2/5.0.0/UML#//Package/packagedElement"/> </containerConfiguration>
<ruleConfiguration xsi:type="rulebased:AndRuleConfiguration"> <composedRules xsi:type="invariantcontainerrule:InvariantContainerRuleConfiguration"> <permissions containerType="<my.container.type>" permitted="true"/> </composedRules> </ruleConfiguration>
The Container Configuration is used to specify what ECore::EReference to use when multiple containing features are possible on the same metaclass.
For instance, when one want to create a UML::Behavior to a UML::State, there are three possible containing features: UML::State::entry, UML::State::exit, UML::State::doActivity. In this case, one could use the Container Configuration to force its ElementType to use one of this three. If not specified, the ElementType Framework will look for possible containing features and use the first it founds.
Therefore, this won't address your need. What you most probably need to do is to look at the rule-based elementtypes. You'll find usage of these in org.eclipse.papyrus.infra.types.tests\model\elementtypetest.elementtypesconfigurations.
Regarding the empty dialog, it is the expected behavior. Indeed, to populate this dialog, EMF seeks for all Ecore::EReference available in the ResourceSet. Therefore, if none is found (because the UML metamodel is not loaded) the dialog is empty. By defining the EReference manually in the elementtypeconfiguration model you indirectly added the UML metamodel to be loaded in the ResourceSet. Instead, you could just use the "Load Resource..." menu item available in the context menu when you right click in the editor.
HTH