Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Oliver F. on October 23, 2008, 03:18:11 am
-
Lately I came across the idea of using patterns to provide architects with ready to use component structures (meaning a component with parts, ports and provided interfaces).
That worked including importing the pattern in the resource view.
The next step caused some head scratching until now because I have not found an answer to the question:
Why can I include a pattern in a MDG technology (there is even a dialog to select it at creation time and it appears in the XML) but it never gets automatically imported with the MDG technology ?
Do I really have to manually deploy it for every developer in question ?
Besides that trying to merge the pattern with an existing component (by moving it onto a component element and changing "create" to "merge") immediately grays out the ok button.
That looks rather suspicious to me.
Comments are welcome.
Oliver
-
When you import a technology you should find you patterns under the MDG technology node in the resource browser.
Selecting merge automatically disables the ok button because you have to select what you want to merge with.
-
Patterns also appear in the Tasks Pane window (Ctrl+Shift+9): click the "More Tasks..." button and select "Model Patterns", the last item on the list. (I think it's very unlikely that anyone will find that in a month of looking, so I'm currently lobbying to have patterns appear in the toolbox).
-
When you import a technology you should find you patterns under the MDG technology node in the resource browser.
Selecting merge automatically disables the ok button because you have to select what you want to merge with.
Well, according to you (Sparx) we should not import technologies but either copy the file into the technologies folder or use the MDG technologies settings dialog to add it from a URL or file path. In neither cases the pattern appears.
However Simons advice with the "More tasks" pane brought me to a view in which the pattern appeared right above tge GoF patterns, though it is not shown in the normal resource view.
Regarding the merge issue, I had selected an exisiting (and locked for writing) component before I dropped the component pattern over it, but the OK button was grayed out.
Oliver
-
However Simons advice with the "More tasks" pane brought me to a view in which the pattern appeared right above tge GoF patterns, though it is not shown in the normal resource view.
Consistency, Consistency, Consistency! TM
I guess, I'm baaaack...
Paolo
-
Sorry, I only mentioned where to find them when imported because that is what you suggested you had done.
-
Sorry, I only mentioned where to find them when imported because that is what you suggested you had done.
Yes, but that does not answer the question, why I can include it in a MDG technology but it is never seen anywhere besides that obscure pattern dialog hidden deeply in the Tasks pane ;)
I believe I will file a feature request for the toolbox...
And it is still not obvious to me how to merge a component pattern with an existing component. What am I missing ?
If anyone can shed some light on this that would be great.
Oliver
Oliver