Menu
▾
▴
#496 OpenJUMP 1.15 freezes on loading project files from differing versions
as described by Peppe on the mailing list
"
On loading project files saved with different versions of OpenJUMP.
There is a break after OpenJUMP 1.5 and before OpenJUMP 6363 on
saving/loading project files.
a) OpenJUMP 1.5 freezes on loading project files saved at least with
OpenJUMP 6363 and 6370
The console (I use Linux) doesn't show any warning.
b) OpenJUMP 6363 and 6370 cannot load project files saved at least with
OpenJUMP 1.5 .
The console doesn't show any warning.
c) OpenJUMP 6363 can load project files saved with OpenJUMP 6370 and vice
versa
"
I could open a project saved with 1.15 with r6370 and viceversa. My project contained a few vectors, and a geotif imported as an image and imported a second time as a sextante image.
On the other hand, I get some problems if csv data is included in the project due to a breaking change I did. Not sure I can fix the bug about saving a csv in the project without breaking, but I'll have a deaper look. Before, I'd like to have more precision about your or Peppe test. What kind of datasources did they include ? csv/wkt ? Could you share the jmp files ?
Trying to reproduce the problem with peppe's test project, I firstly changed all resources absolute paths. After that, I could not reproduce the problem. Changing the paths can be done through the UI except for referenced-image, as the path is in the feature attribute and is store with an absolute path. Would need more details about how to reproduce the bug. Is there a specific layer which cause the problem ? Could it be a linux specific problem ?
If the problem is between 1.15 and r6370 (title is about 1.15 while report is about 1.5 which seems very old!), I can still not reproduce it. I now tried between 1.15 (r6241), r6335 and r6370, with windows and with linux (windows + wsl/ubuntu).
Comparing jmp files, I noticed a small difference between the first jmp file produced after importing data, and jmp file produced after a load from an existing project. But none of these difference prevent another version from opening the project correctly. These differences seem more between reading and writing a jmp file. Just report it to remember :
vector layer : identical
referenced image layer :
first : the ColorThemingStyle includes a DefaultStyle wrapping a vertex style
second : the ColorThemingStyle includes a DefaultStyle with no vertex style
raster layer :
first : a tag <value class="">null</value>
second : the same tag as <value class="">
first : file path is in <imagefilename> tag and again
in the <metainformation><metadata> with the key file-name
second : tag <imagefilename> is the same, but metadata has no key "file-name"</imagefilename></metadata></metainformation></imagefilename></value>
Hi Michael, can you send me the files you used as first test? I will try on my side
The second test I made is much better. I used your files, but I deleted jmp files and restarted from scratch :
Try to load 1.15.jmp from 6370 and the other way : OK
I observed two problems though :
1/ when saving the jmp, tiff imported as image is considered as a layer without source and oj wants to save it as a jml/shp
2/ tiff imported as image have their absolute name in an attribute so that there is no way to read it correctly if the data is moved to another place. Maybe we should have an option to save paths as relative paths.
But none of these problems seem related to your report.
tag it as to be solved in the future as it's unclear what the problem is, if at all something on our end.
Ede, did you ever reproduce the problem ? Peppe, can you reproduce it ? If not, I propose to open another ticket about saving raster in a project and to close this one.
as i wrote directly above your post. nope.
I still have problems.
I attached an image of what is going on on the view when I try to open a project made with OJ 1.15 with OJ 6477.
Nothing happens.
Peppe, do you get this problem with the project you sent us (project.jmp and project-6363.jmp) ?