[Issue 6383] New - MalformedXMIException on too large XMI files
| Newsgroups | gmane.comp.lang.uml.argouml.issues |
|---|---|
| Message-ID | <[email protected]> |
http://argouml.tigris.org/issues/show_bug.cgi?id=6383
Issue #|6383
Summary|MalformedXMIException on too large XMI files
Component|argouml
Version|0.32.2
Platform|PC
URL|
OS/Version|Windows Vista
Status|NEW
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|Model
Assigned to|bobtarling
Reported by|sdeniaud
------- Additional comments from [email protected] Thu Nov 3 09:42:52 -0700 2011 -------
When importing a too large XMI file, ArgoUML raises a
javax.jmi.xmi.MalformedXMIException exception (see the stacktrace at the end of
the report).
To simulate a large model, I've created 2 XMI files, one with 1309 methods that
can be loaded by ArgoUML, the second one is the same one but with one more
method (1310) and can't be imported with ArgoUML.
If needed, I can provide you with these two files.
Error occurred at : Thu Nov 03 17:37:37 CET 2011
Cause : org.argouml.model.XmiException: javax.jmi.xmi.MalformedXMIException
at org.argouml.model.mdr.XmiReaderImpl.parse(XmiReaderImpl.java:337)
at org.argouml.persistence.ModelMemberFilePersister.readModels
(ModelMemberFilePersister.java:273)
at org.argouml.persistence.XmiFilePersister.doLoad(XmiFilePersister.java:261)
at org.argouml.ui.ProjectBrowser.loadProject2(ProjectBrowser.java:1617)
at org.argouml.ui.ProjectBrowser.loadProject(ProjectBrowser.java:1543)
at org.argouml.ui.LoadSwingWorker.construct(LoadSwingWorker.java:89)
at org.argouml.ui.SwingWorker.doConstruct(SwingWorker.java:153)
at org.argouml.ui.SwingWorker$2.run(SwingWorker.java:281)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jmi.xmi.MalformedXMIException
at org.argouml.model.mdr.XmiReaderImpl.parse(XmiReaderImpl.java:294)
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2872471
To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.