Hi I'm also feeling that VP is the error originator here.
However the XMI importer in Argo is also not giving very much clue (or at least the error message isn't), e.g. line number, if such a thing is possible, or perhaps the location in the XML structure, or some other kind of clue as to where the error is. This would help analyze the XMI input file and distinguish between errors from other tools which generate wrong XMI, and errors in Argo XMI importer itself. Best wishes, Vasile RUS -----Original Message----- From: Tom Morris [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 3:52 AM To: [EMAIL PROTECTED] Subject: RE: [argouml-users] Trying to import XMI 1.2/ UML 1.4 from Visual Paradigm I had a quick look at this using an evaluation version of Visual Paradigm and it's definitely encoding FinalStates wrong. The workaround that you mentioned: > I replaced in VP all the graphical symbols for Final > state with a regular state which I called Final. worked for my simple 3 state statemachine test, so I suspect that your second error message > XMI format error : org.argouml.model.XmiException: > javax.jmi.xmi.MalformedXMIException: > javax.jmi.reflect.TypeMismatchException is from an unrelated error in the the XMI file. That could be simple to fix too, but these things are like peeling an onion and we won't really know how many problems there are until we're done. Hopefully Visual Paradigm didn't screw up too many other things! Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
