gvSIG bugs #3990: Build 2413 doesn't open previous projects - CORRUPTED PROJECTS? - Application: gvSIG desktop - gvSIG

gvSIG bugs #3990

Build 2413 doesn't open previous projects - CORRUPTED PROJECTS?

Added by Andrea Antonello over 8 years ago. Updated over 8 years ago.

Status:

Closed

% Done:

Priority:

Urgent

Spent time:

Assignee:

Daniel Martinez

Category:

Application

Target version:

2.3.0-2416 (rev. org.gvsig.desktop-2.0.122)

Severity:

Critical

Add-on version:

gvSIG version:

2.3.0

Add-on build:

gvSIG build:

2413

Add-on resolve version:

Operative System:

Add-on resolve build:

Keywords:

Proyecto:

Has patch:

Hito:

Add-on name:

Unknown

Description

I just downloaded the latest build (gvSIG-desktop-2.3.0-2413-devel-lin-x86_64-standard) and tried to open an old project.

It is:

not opening it
not giving any error message to the user (that would be necessary)
throwing a lot of exceptions about relative paths

I have seen the relative path problems already with previous build. It happened quite often that my project got corrupted and was useless.

This time tested on linux but previously seen the same error on windows.

Log is attached.

gvSIG.log (473 KB) Andrea Antonello, 01/11/2016 09:48 AM

Related issues

History

#1 Updated by Antonio Falciano over 8 years ago

Ciao Andrea,
I believe that the issue you report depends by the specific content of your project. I've just tried to open an old project and I can open with build 2413 in win64, even if it loads only vector layers. The raster ones are not loaded because of an URISyntaxException.
In your specific case, grepping the "can't fix" messages from the gvSIG.log we have:

Can't fix relative paths in MapCache
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheService
Can't fix relative paths in MapCacheFormat
Can't fix relative paths in MapCacheCache
Can't fix relative paths in MapCacheCacheType
Can't fix relative paths in MapCacheCacheMbTiles
Can't fix relative paths in MapCacheCacheSqlite3
Can't fix relative paths in MapCacheCacheDiskLayout
Can't fix relative paths in MapCacheCacheDisk
Can't fix relative paths in MapCacheCacheMemcache
Can't fix relative paths in MapCacheFormatType
Can't fix relative paths in MapCacheFormatPNG
Can't fix relative paths in MapCacheFormatJPEG
Can't fix relative paths in MapCacheFormatMixed

The main consequence is that gvSIG Can't perform action 'application-project-open' and this is Caused by: org.gvsig.tools.persistence.exception.PersistenceClassNotRegistered: Class not registered in manager 'MapCache'.. So the issue depends by MapCache class or related properties that are not persistent in build 2413.
In conclusion:

the most part of the old projects can be opened, but there are some different issues (URISyntaxException, MapCache persistence, ...) with (locale or remote) raster layers;
being gvSIG projects version specific, some incompatibility issue may occur. Thus an old project can be considered not fully compatible with newer versions, but not corrupted. We can corrupt it only if we overwrite it.

#2 Updated by Andrea Antonello over 8 years ago

Hi Antonio,

I believe that the issue you report depends by the specific content of your project. I've just tried to open an old project and I can open with build 2413 in win64, even if it loads only vector layers. The raster ones are not loaded because of an URISyntaxException.

Well, GIS is also made of rasters, so I guess this issue has a reason to be opened, right? :-)

In your specific case, grepping the "can't fix" messages from the gvSIG.log we have:
[...]
The main consequence is that gvSIG Can't perform action 'application-project-open' and this is Caused by: org.gvsig.tools.persistence.exception.PersistenceClassNotRegistered: Class not registered in manager 'MapCache'.. So the issue depends by MapCache class or related properties that are not persistent in build 2413.
In conclusion:

the most part of the old projects can be opened, but there are some different issues (URISyntaxException, MapCache persistence, ...) with (locale or remote) raster layers;

being gvSIG projects version specific, some incompatibility issue may occur. Thus an old project can be considered not fully compatible with newer versions, but not corrupted. We can corrupt it only if we overwrite it.

I can agree about the reason this happens, but I can't agree about the fact that this is not a bad bad problem, if not handled.

If this can't be resolved right now, then I would expect that the user is warned about the fact that he is loading a potentially incompatible project.

I know gvSIG wants to be backward compatible on many things, I think projects should be one of that. If not, at least warn the user. I had several times problems with project that then didn't save any more. Which means corrupted.

Your final statement about incompatibilities and corruption only on save... well, it is exactly what will happen to any new user that is not aware of that. They will try to do "something", possibly saving and breaking things.

#3 Updated by Antonio Falciano over 8 years ago

Hi Andrea,
I'm agree with you. This kind of blocking issue should be fixed if possible within the final release or handled in a better way (i.e. user warning) in order to avoid the project corruption. ;) Fortunately it seems that the issue due to the URISyntaxException has been fixed yet in #3952 by Joaquín. So fixing relative paths or some plugin persistence remains.