Code Engineering: Out of Resources

[Uffe]

Hi!


If you reverse-engineer a large number of classes (like the JRE rt.jar) and ask for logical diagrams to be created, pretty soon you run into error messages due (presumably) to the fact that you run out of windows.

This in turn is because each diagram is created when needed, entities are added as they appear, but the diagram is not closed until it's been Layouted (alright, laid out), which is only done after all the entities have been imported.

Wouldn't it be better to (have the option to) close the diagram after each entity has been added, thus ensuring you never run into the too-many-windows problem? It might take longer, but you'll get there in the end.

Or is there some other workaround?


/Uffe

[«Midnight»]

I wonder where this is coming from. I've imported the .Net libraries without incident, and they are similar in size and complexity.

I've not done so for quite a while though. Perhaps a new 'limitation' was introduced in the intervening EA versions.

Does the Java import allow you to choose the discovery method? [.Net imports can use reflection or reverse engineer the code.] If so, try the other option. Way (way, way) back when binary imports were brand new I ran into trouble with a few .Net libraries using one method. The other method worked, so I didn't worry too much about it. Sparx tweaked the import code when I reported the problem, which solved it (at the time).

David

[Uffe]

No, no discovery options. You can choose whether to create the diagrams, whether to synchronize or overwrite existing classes, and whether to import Private members, but that's it.

I've only got 2 GB RAM on this machine, maybe that's the problem.

[«Midnight»]

No, I doubt it. 2 GB should be much more than enough.

I think this needs to go to Sparx Support. With luck they will be able to duplicate the problem and find out what's going wrong.