#25 Extension mechanism for ea_uml2exporter
Hi!
I've been thinking a while about some requirements of my project we can't fulfil with current implementation of ea_uml2exporter. I'm reluctant to modify ea_uml2exporter to do anything more than EA to MDT/UML transformations, but for some cases it doesn't exist another option. E.g. if I want to create a special element, like a stereotyped ValueSpecification for a specific value, I don't have another option to implement a rule in ea_uml2exporter which would be dependant to my project and the profile I'm using.
Perhaps some kind of extension mechanism for ea_uml2exporter would be useful for that scenario. For example, if there were such mechanism I could contribute a visitor for some specific elements, so I could manipulate its transformations or even override the default ones. My main idea is to keep the general "MDT/UML to EA" transformations decoupled from our hypothetic project specific transformations.
What do you think about that?, have you ever had the same need I'm having?, it is feasable?
Cheers!
Hi David
The basic architecture of the exporter consists of an easier to use interface for model elements of EA (ea_com_interface). Based on this interface you can write your own export utility.
If I understand correctly, you like to have an extension mechanism for replacing current export implementation of an element with a specific one. Let's say: for each class with stereotype <<MyStereo>> I want to create a special element in UML or in Ecore.
Or
The current export functionality has to be extended with extra code by injecting additional exportation code after the element is transformed.
Both are possible. Make a prototype of it and send it to me for discussion.
Regards,
Ueli