Persistence of data in TDB

[GoogleCodeExporter]

There seem to be issues related to persisting the data reported on the list 
[1]. See issue 344 [2] for earlier problems.

Data should not be just be persisted when shutting down the JVM. Even when the 
application would crash data put in hours before should still be there. This 
seems to be not the case but needs to be tested more thoroughly.

We need to understand (and then document) how Jena takes care of these issues.

[1] 
http://groups.google.com/group/simal-contributors/browse_thread/thread/c7300f362
9d9764d 
[2] http://code.google.com/p/simal/issues/detail?id=344

Original issue reported on code.google.com by sander.v...@oucs.ox.ac.uk on 2 Feb 2011 at 4:11

• Blocked on: #416

[GoogleCodeExporter]

Original comment by ross.gardler on 7 Mar 2011 at 9:17

• Added labels: Milestone-0.3, Priority-Critical, Usability
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by sander.v...@gmail.com on 12 Apr 2011 at 1:54

• Added labels: Slotted
• Removed labels: ****

[GoogleCodeExporter]

This issue was updated by revision r2240.

There was something fundamentally wrong with how we save the data which is 
related to a workaround I had to create because Wicket works with Lists whereas 
we have Sets everywhere. As a result changes are not correctly persisted. 
Working on a better solution.

Original comment by sander.v...@oucs.ox.ac.uk on 14 Apr 2011 at 9:40

• Added labels: ****
• Removed labels: ****