collection.xml not saved after shutdown, only collection_exit.xml

[mats.ahlgren@…]

collection.xml not saved after shutdown, only collection_exit.xml is saved

Replication: - Open Jajuk - Change some song ratings - Close with alt-X - Open ~/.jajuk/collection.xml -- search for the track name, and notice the metadata has not been updated - Open ~/.jajuk/collection_exit.xml -- this seems to be the most up-to-date

This may be intended behavior; if so, sorry, please close this ticket.

System: Linux on OpenSuse? 10.3 with Java 1.6.0_18

[bflorat]

It is indeed the expected behavior : basically, we manage the "transactional" aspects of collection commit this way :

• We write to a collection_exit.xml file
• If still ok, we write a void exit "proof" file (exit_proof)

At startup, if the exit_proof is there, it means that the previous commit was ok, we move the collection_exit.xml to collection.xml and we parse collection.xml

(it's actually a bit more complex as we have to deal with backup files in case of further issue, see Collection class code if interested)

[mats.ahlgren@…]

That seems perfectly fine. I guess I was just trying to say, "a user who is interested in modifying / backing-up / restoring / copying / viewing his collection.xml file ought to know that the 'real' file is collection_exit.xml+exit_proof".

This doesn't seem important enough to risk breaking something by rewriting code though. Nevertheless, I would humbly suggest a "README-if-modifying-collection" file in .jajuk which contains the text:

"The 'real' collection.xml file is collection_exit.xml. If the file exit_proof is missing though, then... [further info]"

[issue kept as closed]

[bflorat]

A documentation is already available at [1]. By experience, We don't like much scattering documentation over many places so we put everything into our wiki manual.

[1] http://jajuk.info/index.php/Using_devices#Collection_backup_and_restore