Linked Documents - MDG Technology - Problems!

[Israel Aono]

Good Afternoon!

I am developing a mdg technology at the company I work, but I am having some problems to "link" a Linked Document to a stereotype.

I tried to create the linked Document both on the Stereotype and the metaclass, but neither worked. I also exported the stereotypes as UML Profiles.

" I imported the UML Profile and the Linked Document Template on a new project when testing the new MDG Technology. Is this really necessary ? "

The MDG TECH is working fine (Stereotypes, Diagrams, ToolBoxes...) but without the Linked Documents attached.

Am I forgetting Anything? I really spent some time trying to  figure this out, but a I just couldn´t....I also couldn´t find an answer in the forum. Can anyone help me on this?

Thanks All!

[qwerty]

I can't help with the linked document. If you don't get an answer from some guru here you are well served to send a support request to Sparx (bottom right of this page).

Regarding the cumbersome testing procedure: that's how it is. Even worse that you don't get any meaningful error message if something is wrong with your MDG. Blood, sweat, tears and curses....

q.

[Eve]

You can include a linked document template in the technology (there should be a checkbox for it in the wizard) but to my knowledge you can't link it to a stereotype at all.

[Uffe]

Same here, I'm pretty sure there's no way to join a linked document with a stereotype in an MDG Technology. You could write a simple Add-In that creates a document when the corresponding element is created.

As regards testing, when developing an MDG Technology and/or an Add-In, I always do my testing on a virtual machine (VirtualBox if I can choose for myself, otherwise whatever the client uses).

On that virtual machine I have EA and a test project, and the MDG search path is set to a shared directory on my development machine, which is where I direct EA to store the MDG Technology when I run the creation wizard.

This way, I just restart EA on the test machine and the new MDG Technology is in place. (With Add-Ins I have to run through an installation procedure of course.) Virtualization is even more important when defining searches, as those are available to all projects on the machine where they're created so it's important to make sure they're actually included in the MDG Technology.

[Israel Aono]

Thank you All,

that is what I need: "You could write a simple Add-In that creates a document when the corresponding element is created"

_ I tought I could just add the correspondent document to the element when creating the MDG Tech.

Uffe, is the document you mentioned a linked document, correct?

Simon, I added the linked doc template to the MDG Tech, but what I need is what Uffe described. Create a custom linked doc when adding an element.

Regards...

[Israel Aono]

Hi All,

one more thing... I have an axample running where I work exaclty how I described, when an element is added, a custom linked document is created. But studyind the project, there isn´t any Custom Add-in or Script implement, that´s why I tought its was implemented in the MDG Tech.

I will keep trying, and analysing the xmi I have,  any news I get back...

Cheers.

[KP]

I think patterns is the way to go. If you create a diagram with a single element that has a linked document, you can save the diagram as a pattern, include it in your technology, and add it to your custom toolbox so that it can be dropped onto other diagrams.

[Israel Aono]

Thank you KP,

patterns really worked fine.

I don´t even need to add the stereotype to the Toolbox, just the respective pattern...excellent!

Israel.

[Israel Aono]

Still, the other guy manage to implement that without Patterns, only UML Profiles and Linked Doc Templates...Don´t know how ... yet!

Any ideas please contact me,

cheers !