Re: Cannot open file

One more hint for recovering things is to look for a file name
<project>.zargo~0.24 in the directory where the project that you
opened with 0.26 is located.  It should contain a pre-upgrade version
of your project.

A possibly related bug report is
http://argouml.tigris.org/issues/show_bug.cgi?id=5434
The bug concerning the bad error message is
http://argouml.tigris.org/issues/show_bug.cgi?id=5499  It is fixed,
but of course that doesn't help the old versions which are out in the
field.

Tom

On Thu, Nov 13, 2008 at 9:09 AM, Tom Morris <[email protected]> wrote:
> Hi Anh Tu,
>
> Sorry to hear about the problem.  We should be able to recover your
> file for you.  Could you please open a bug report and attach your
> project file (.zargo or .uml) to it and we'll have a look.  If the
> file is sensitive, you can email it to me or one of the other
> developers instead of posting it.
>
> You could also try the recently created beta version 0.26.1 to see if
> it fixes your problem.
>
> More comments in-line below:
>
> On Thu, Nov 13, 2008 at 3:37 AM, Anh Tu Sam <[email protected]> wrote:
>
>> I've been working on that project file
>> for almost half a year and used ArgoUML 0.24 for this. Sometimes I also used
>> the Eclipse plugin ArgoEclipse, which is the 0.22 release.
>>
>> A few days ago I started to use 0.26 over Java web start. Since then I
>> cannot open my project file anymore, no matter which version I use. When
>> trying to open with 0.24 or 0.22 I get the short error message
>> "dialog.error.file.version".
>
> The 0.26 version introduced a new on-disk format which the older
> versions can't read.  The application probably should have warned you
> that it was updating the version and that you wouldn't be able to open
> it in older versions of the program.  The malformed error message is a
> bug in 0.24 which is trying to tell you that you have an incompatible
> version.
>
>> When trying to open with 0.26 I get a much
>> longer error. I pasted this error here: http://dpaste.com/90426/
>
> Please include this message in the bug report when you create it.  It
> looks like a known problem, but it's good to have all the information
> in one place so that it can be reviewed by whichever developer looks
> at the problem.
>
> Tom
>