Thanks for the reply.

I attach a .zargo file with a simple sequence diagram, and an SVG image that shows roughly how the diagram is supposed to look (not generated with ArgoUML, so the exact layout is different). You can open the SVG file with Firefox.

The two files are very small, 4 and 3 kB respectively, so hopefully no-one minds that I attach files.

The .zargo file works in ArgoUML 0.12. Calls to self are not displayed correctly (Foo.<init> and Foo.doIt), but that is a minor problem.

In 0.24, the file opens, but only shows up as a collaboration, there is no sequence diagram displayed.

The .zargo file is generated using Novosoft UML API 0.4.20. I heard from Thomas N. that you are now using Netbeans MDR instead. The file format was found through trial-and-error, as I recall I did not look at the ArgoUML source code.

Looking at the 0.24 debug log file, it seems that ArgoUML upgrades the file from version 1 to version 5 using upgrade{2-5}.xsl. It also says "XMI file doesn't appear to be UML 1.4 - attempting UML 1.3->UML 1.4 conversion". Then follows a number of errors, saying things like "Property 'remove' for class 'Model' doesn't exist in metamodel" for a lot of different properties: 'see', 'deprecated', 'since', 'version', etc. Don't know what to make of that. After that only debug messages. There are no exceptions thrown when opening the file.

If anyone has any idea about the best way to support ArgoUML 0.24, I would be very thankful. Thomas N. thought that it might be necessary to start from scratch. If so, what would be the best API to use? Bob Tarling mentioned a "new Sequence2 model", and Thomas N. a "model API" on top of Netbeans MDR. Any pointers greatly appreciated.

Thanks and best regards,

Henrik Arro

At 01:05 2008-08-16, Tom Morris wrote:
On Mon, Aug 11, 2008 at 11:30 AM, Henrik Arro <[EMAIL PROTECTED]> wrote:

> Any ideas about how best to update the generated file format to support
> 0.24?

If you can provide an example of the output that you're generating
now, someone may be able to provide more concrete feedback as to what
the problems are and what needs to be changed.  A lot has changed
since 0.12 and the sequence diagrams have been particularly
troublesome, going through at least a couple of reimplementations.
Because ArgoUML encodes the figures' class names directly in the
output file PGML file and reloads them using reflection, it's
particularly fragile in the face of changes.

Did you look in the argouml.log file to see if any errors/warnings are
being logged?  If there's nothing there, running ArgoUML with debug
logging turned on may provide more insight into what the problem is.

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.6.3/1614 - Release Date: 2008-08-15 17:29

Attachment: test.zargo
Description: Binary data

<<attachment: test.svg>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to