TAPAAL 1.4 fails when opening a DEV version net
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TAPAAL |
Invalid
|
Low
|
Unassigned | ||
1.4 |
Fix Released
|
Low
|
Kenneth Yrke Jørgensen | ||
VerifyTAPN |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Try to open a net created in TAPAAL DEV using TAPAAL 1.4, this fails with an exception. TAPAAL should report the file can be read and give a pointer to open it using TAPAAL DEV
<code>
[Fatal Error] ObjectList.xml:3:1: Premature end of file.
org.xml.
Workaround: delete the xmlns attribute from the PNML root node. Probably not ideal, to be fixed when time allows.
runtime except
java.lang.
at pipe.dataLayer.
at pipe.gui.
at pipe.gui.
at javax.swing.
at javax.swing.
at javax.swing.
at javax.swing.
at javax.swing.
at java.awt.
at java.awt.
at javax.swing.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.security.
at java.security.
at java.security.
at java.awt.
at java.awt.
at java.security.
at java.security.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
at java.awt.
Caused by: java.lang.
at pipe.dataLayer.
... 39 more
</code>
Related branches
Changed in verifytapn: | |
status: | New → Invalid |
Changed in tapaal: | |
milestone: | none → 1.4.3 |
importance: | Undecided → Low |
summary: |
- TAPAAL 1.4 fails hard when opening a 1.5 nets + TAPAAL 1.4 fails when opening a DEV version net |
This is obvious since the XML structure for the nets has been changed in TAPAAL 1.5 to make it easier to parse... TAPAAL 1.5 is backwards compatible with models created in TAPAAL 1.4, but in my opinion it doesn't make sense to spend time making TAPAAL 1.4 forward compatible with TAPAAL 1.5 models...
If you start down that road you are just introducing major maintainance issues whenever we add something to the model or make small changes to the XML structure in the future... For instance, say you introduce a new modelling feature in TAPAAL 1.6... Then you would have to add support for the same feature in 1.4 and 1.5... On the next release you introduce a small change in the XML structure, now you have to do maintainance on TAPAAL 1.4, 1.5 and 1.6 to support this change. I think this time would be better spent fixing bugs or adding new features... Backward compatibility is all we need in my opinion...