The main XSLT.

An identity XSLT imported by MagicDrawAssociationClassNormalizer.xsl

thanks for sharing this with us, very clever solution

do you have any idea how this could be integrated best with AndroMDA ? or would we simply point users to this issue if they want to make it work for them ?

We could set up a pipeline in the core or something for things like this (for when people want to transform the XMI with XSLT docs or something, since it's happened more than once), we just create an option that allows people to specify these XSLT documents (and the order in which they should be applied) and we apply them to XMI before its loaded by MDR...what do you think?

yeah sounds good, but the pipeline should not alter the original XMI, it should just feed a transformed one to AndroMDA

this would be excellent to have in the core

Yeah that's what I meant...it just modifies the XMI in memory, not on disk before the repository loads it...I'll create an issue.

this issue is now followed-up by issue CORE-56

Thanx for the compliment, this was the least I could do in return for the valuable feedback you gave to me :)

As for the integration to AndroMDA, I'm not sure, on the one hand, it is a hack related to a specific limitation of a specific vendor's tool, but on the other hand, MagicDraw is the tool of choice to use with AndroMDA and except for that limitation a really great modeling tool worth the care.

As far as I'm concerned, I included this XSLT as an ant:style based goal in a XMI specific maven plugin (whose main purpose is to manage xmi.zip type artifacts like maven-jar-plugin does). Maybe, this could be the way to go for AndroMDA too. I can share that plugin with you if you're interested. What's more, I believe this would be a usefull addition to the andromda maven plugins ;)

There is also CORE-56, which is a great idea. In that paradygm, the hack could be available as an optional pipeline transformer, that the user could include in the pipeline if he wants to.