thomaskilian

Looks like a known issue: you have to reload packages (almost always at it seems). I just had this problem with relations between controlled packages which were only loaded correctly after a 2nd load of all controlled packages.

thomaskilian

Michael,I'm sorry but I can't be of much help. To me it just sounds like there is a basic flaw in EA's VC. Loading a package from XMI leaves EA at first in a more or less inconsistent state. Reloading packages then clears this state. I would report your observation as a bug since I would expect that loading a root node would refresh all children too.

As I know that I have to live with some (!) of these flaws I decided to have my work-around (as convenient as possible).

thomaskilian

Hi Michael,actually I might be a step ahead. In the beginning I also had controlled-controlled packages (the root was controlled and sub-packages too). Then I found out that this was not working well and simply stepped to just having one level of controlled packages. I further turned off EA VC and simply exported these packages to XMI. I save/load these manually and VC the files directly with svn. Quite some drawbacks as stub-saving is not possible that way. Also I have quite huge packages this way. I remember the days with Rose where that was much, much more convenient (I wouldn't like to go back, though).

but they way you go is a bit dangerous in a team environment, isn't it.

Nobody knows which package is exported, imported, which version, etc.

If that is the way to handle it, it is a criterion to decide using another tool.

There are a couple of things with reverse engineering and nested controlled packages.If we have this additional problem, that this tool is not usable in a team environment with more than 2 developers.

Currently we are 17, using other sub models from other teamswhere hundreds of developers are working on. And if we are not able to conveniantly which means correctly checkout/checkin than we have to switch, I fear.

This is a tremendous handicap.

Michael

Logged

thomaskilian

Yes, I know. But when working with a larger team you anyway need a change manager to have a hand on it. So he is the one to do the integration work with the different deliveries. In a small team you can simply rely on direct communication (I mean you have to tell them this story every day again: Talk to each other). The main problem I see is the limited number of packages you can actually control. Either you stick with top level packages (not very flexible) or you give a kind of a predefined fixed stub tree. Neither is optimal.

Sparx, can you hear me? Please allow stub saving for XMI also in non VC context!

thomaskilian

I wouldn't care to much about the devolpers as they ought to read the model only, not change it. Now for the designers/architects: if you don't have a change manager you're really pissed. I could think of having an add-in to complete the job that EA does not do. I remember Paolo wrote something like that in the thread I mentioned.

thomaskilian

Yep. Just the architects change the model. I guess that different needs lead to different usages. I probably can't help much except for the advice to write appropriate add-ins. You can produce quite good remedies for missing/mal-function in EA.