Author Topic: Import package as root node no longer possible? (Read 9630 times)

ch@SVDO · « **on:** December 10, 2007, 02:38:11 am »

Hi,
does EA 7.0 not longer provide the feature to import a previusly exported package as root node?

I think in v6.5 a dialog appeared if you tried to import a package that has been a root node in another project, asking if the imported package should again be placed on root node level.
Did Sparx remove this feature with v7.0?

With best regards,
Charly

«Midnight» · « **Reply #1 on:** December 10, 2007, 04:58:45 am »

Charly,

I think we saw something related to this in the past few weeks. The other report made it sound like EA was only handling a subset of import scenarios relating to root packages. I don't remember the details.

I believe a bug report was submitted, but since I'm not the originator of the post, I cannot say for sure.

You might want to search the forum to see if you can find the other thread. It would be within the past month.

David

Jan ´Bary´ Glas · « **Reply #2 on:** December 10, 2007, 05:05:46 am »

I am working with this feature and it is changed somehow. This works:
If you export root package, EA asks when importing if it should be treated like a root or not.

«Midnight» · « **Reply #3 on:** December 10, 2007, 05:10:48 am »

Hi Jan Glas,

Are you saying that root -> root works (or at least shows the dialog), but not otherwise?

My recollection is that before EA 7.x we could export any package, then attempt to import it as a root, and we'd get the expected behavior, including the warning dialog. Perhaps either the behavior or the (presentation of the) dialog has changed in 7.x. I can think of scenarios where I might want to 'promote' part of a model to become a root node of a new model. It sounds like this might be disappearing from EA.

David

Jan ´Bary´ Glas · « **Reply #4 on:** December 10, 2007, 05:14:38 am »

Sounds like. In fact I didn't try it. The described scenario is what I need and use. But for sure it worked in v6.5 otherwise as well.
Someone to try? ;-)

Eve · « **Reply #5 on:** December 10, 2007, 12:59:23 pm »

I don't remember when it was changed, but until recently EA would allow you to import any Root or View (The top two levels of hierarchy) as a root node.

Now I believe that it checks to ensure that the package being imported doesn't contain any diagrams or elements first. This is because root nodes can't contain element or diagrams directly but views can.

«Midnight» · « **Reply #6 on:** December 10, 2007, 05:36:15 pm »

Simon,

That certainly makes sense.

I notice that there is an (old?) IsModel attribute of the Package class, and I keep thinking this is also reflected in the schema (but I have not checked). Perhaps this was used at some time for something like identifying the top of a project tree, before EA handled namespaces.

Who knows...

David

thomaskilian · « **Reply #7 on:** December 11, 2007, 01:49:04 am »

Quote

...This is because root nodes can't contain element or diagrams directly but views can.

Which does raise the question: why? I remember in early versions it was possible to have diagrams on top level. Honestly I do not see any sense in this restriction.

«Midnight» · « **Reply #8 on:** December 11, 2007, 08:12:14 am »

UEE - User Experience Entropy.

Supported by the EAUI.

ch@SVDO · « **Reply #9 on:** December 12, 2007, 02:24:37 am »

Thank you all for your quick replies.
@Jan Glas: The thing is that EA does not even ask me (when importing a root node from another project) if the import should be placed on root node level. Instead, EA directly puts it below the root node or package which is currently selected in the target project.
I'm using version 7.0.816.

Jan ´Bary´ Glas · « **Reply #10 on:** December 12, 2007, 06:12:33 am »

Quote

The thing is that EA does not even ask me (when importing a root node from another project) if the import should be placed on root node level. Instead, EA directly puts it below the root node or package which is currently selected in the target project.
I'm using version 7.0.816.

I am using 7.0.818 and it is working. Let's wait for 7.1 and we will see.

ch@SVDO · « **Reply #11 on:** December 13, 2007, 05:10:08 am »

Hi Jan,
sorry for troubling you again. I just updated to 7.0.818 and still I can't import a root node from one project as root node within another project.
Would you be so kind as to explain me how you conduct your import click by click?

regards,
Charly

ch@SVDO · « **Reply #12 on:** December 13, 2007, 05:36:58 am »

I just discovered the reason for this strange behaviour: the value for the registry key "AllowXMIAtRootEx" at "HKEY_Current_User/Software/Sparx Systems/EA400/EA/OPTIONS" was set to 0. After I manually switched this value to 1, import of packages on root node level is possible again!
I wonder how this value could have been altered to 0, but at least it works now.
Thanks to you all!

Regards ,
Charly

thomaskilian · « **Reply #13 on:** December 13, 2007, 06:40:46 am »

Seems like the registry offers an additional set of options to tweak EA...

ch@SVDO · « **Reply #14 on:** December 13, 2007, 06:48:31 am »

As EA provides such a registry entry I would normally and consequently expect a possibility to configure the import feature in EA's Tools-->Options-->General. If it is not meant to be configured as an option, why does EA put such an entry in the registry?

Sparx Systems Forum

News: