Re: "clustering" stereotyped dependency ignored by the UML2 MOF tool ?

"Merge" is more like a copy. Clustering is completely different - it is 
more like nesting. You can try to use package inheritance to get closer 
to "merge". But AFAIK you will be the first to use it, so you may find 
some bugs in its implementation in MDR, although we tested it.
Regards,
Martin

SCHNEKENBURGER Remi CRIT wrote:

>Hi Martin,
>
>Thx for your response.
>
>When I said I wanted to import the package, I wanted to use the "merge"
>stereotype defined by MOF2.0. As MDR actually implements MOF1.4, I thought
>that the "clustering" stereotype was the best way to link the packages. I
>have not found a more interesting solution. 
>When I looked to the UML metamodel in Poseidon in a XML file, I've seen that
>the different packages defining UML had a value isClustering set to True.
>That's why I used the "clustering" stereotyped instead of the "import"
>stereotype (that does not exists in the UML profile for MOF for poseidon, if
>i make no mistakes). 
>
>Remi
>
>-----Message d'origine-----
>De : Martin Matula [mailto:[email protected]]
>Envoyé : jeudi 29 juillet 2004 15:47
>À : [email protected]
>Objet : Re: [mdr-dev] "clustering" stereotyped dependency ignored by the
>UML2 MOF tool ?
>
>
>Hi Rem,
>
>SCHNEKENBURGER Remi CRIT wrote:
>
>  
>
>>I have several packages stereotyped "metamodel". These package should 
>>be linked using the MOF element "import". So I use, as explained in 
>>the table, a dependency stereotyped "clustering".
>>    
>>
>
>Are you sure you want to cluster the packages? Or you just want to 
>import them?
>
>  
>
>>When I try to import the metamodel in MDR explorer with Netbeans, I 
>>have the picture representing a link between 2 Metamodels, with the 
>>name given to the dependency. When I am generating the XMI file 
>>representing the metamodel, uml2mof tells that an instance of the 
>>dependency is ignored.
>>    
>>
>
>Yes, that's fine - dependencies are a special case - they are handled at 
>the end of the transformation - the message comes from the first phase 
>of the transformation which correctly ignores them. I agree it is 
>confusing. I guess I should remove the "Ignoring.." messages completely.
>
>  
>
>>Why do I have such a message? Is the metamodel loaded correctly ? I 
>>have seen that these messages are present when there is a hierarchy 
>>between the packages. Is the fact that some packages are nested is 
>>forbidden by the UML2MOF tool?
>>    
>>
>
>No, this is not forbidden at all.
>You can verify that the relationship is really transformed to MOF by 
>loading your metamodel into MDR running in NetBeans 3.5.1 or 3.6 and 
>browse though the metamodel in MDR Browser and check whether you can see 
>the import.
>Regards,
>Martin
>
>  
>