Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - yyz

Pages: [1]
1
General Board / Re: Out of memory error while importing packages
« on: September 14, 2004, 02:30:41 pm »
Ben, Thomas -

Any word on this problem?  I never received a confirmation after filing the bug.

2
General Board / Re: Out of memory error while importing packages
« on: September 08, 2004, 04:21:34 pm »
Bug report filed and supporting files packaged and sent to [email protected]

Look forward to hearing from you!

3
General Board / Re: Out of memory error while importing packages
« on: September 02, 2004, 06:03:21 pm »
There are also issues with applying a stylesheet on export of these very large packages.  I get the same out of memory error but it doesn't typically pull the rug out from under EA as does the import.

I've done some similar tests with applying style sheets to these same XMI files using the apache xalan-java tools and have had good success, although I'm still considered a "newbie" here...  ;)

4
General Board / Re: Out of memory error while importing packages
« on: September 02, 2004, 05:58:38 pm »
Yes, I have opened it in a browser and haven't spotted anything glaringly wrong.  Remember, these files are big so I'm not able to verify every line.

I'm not sure what you mean by "and further the source EA with EA's sanity check?"  

Also, is there something else I can provide to help debug this?  I have several files that will cause EA to fail (crash) very consistantly.

Thanks again for your help.
     

5
General Board / Re: Out of memory error while importing packages
« on: August 23, 2004, 09:55:40 am »
Thomas,

The XML is exported straight out of EA and then imported back into another instance of EA.

6
General Board / Out of memory error while importing packages
« on: August 20, 2004, 05:46:04 pm »
I'm getting the following error while attempting to import a large package (specifically java.* classes reverse engineered and exported using Enterprise Architect):

DAO.database [2004]
Out of memory

After clicking Ok to the error dialog and waiting for the import to finish, I get the following error:

Error: Unknown Transition Source or Target

Version 4.1, build 734 of Enterprise Architect for Windows

Can provide the XML file if needed.

Thanks!

7
General Board / Re: linking to existing diagrams
« on: September 09, 2004, 10:19:00 am »
I had this same problem and finally realized that you need to create the referring diagram first and then the referred-to diagram.  Here's how I've made it work:

1) Create your highest level (most abstract) activity diagram first

2) Add a Subactivity element

3) Double-click the Subactivity element you just added.  This will create a new, blank diagram for the Subactivity.

4) Add elements to the newly-created diagram

If you've already created the subactivity diagram, you can drag that diagram from the Project View (right side of the application) onto the higher-level diagram.

You can also do steps #1 - 3, above, and the cut and paste the contents of your already-created subactivity diagram to the newly-created one.

This wasn't obvious for me either.  Hope that helps.


8
General Board / Re: Access to Java data type and classes
« on: August 04, 2004, 02:28:27 pm »
If you're not happy with the "package::Class" notation used in Class Diagrams, for example, you can add aliases to each of the Java classes you import and tell EA to use those aliases in the diagram.

For example, you can change the alias (select class in Project View, right-click and choose Properties) for the String class to be "java.lang.String".

Then, in the diagram, change it's properties to use the alias (right-click on diagram -> Diagram Properties...  -> Use Alias If Available).

You classes will then be labeled:

java.lang.String

rather than:

lang::String

If you're a UML purist and demand the latter form, it's easy enough to turn off.

Fair amount of scut work to alias all of the classes but it can be automated.

9
Juergen,

Under the "Tools" menu, there is an option "Import Reference Data...".   That will give you what you want.

The easiest way to do this is to first export your glossary (Tools -> Export Reference Data...), modify the exported data and import it back in.

The format of the file is pretty simple.

Pages: [1]