> > Did you test this ? Last time I tried this, db4o wasn't > storing inner > > complex objects and I had to manually store them. > > > > See contexts and properties in Identity.java. > > If this really isn't necessary, you can remove it from there too. > > I did not test it. I thought that one part of the use of db4o > is that you do not have to store inner complex objects manually? > Is it maybe possible to do this with db4o somehow? >
I will use toad's suggestion to fix this: > -----Original Message----- > From: devl-bounces at freenetproject.org > [mailto:devl-bounces at freenetproject.org] On Behalf Of Matthew Toseland > Sent: Wednesday, September 24, 2008 9:14 PM > To: devl at freenetproject.org > Subject: Re: [freenet-dev] [freenet-cvs] r22761 - trunk/plugins/WoT > > On Tuesday 23 September 2008 12:10, xor at freenetproject.org wrote: > > Author: xor > > Date: 2008-09-23 11:10:49 +0000 (Tue, 23 Sep 2008) New > Revision: 22761 > > > > Modified: > > trunk/plugins/WoT/Config.java > > trunk/plugins/WoT/WoT.java > > Log: > > Change the Config class so that it does not store a reference to a > > db4o > ObjectContainer. This is not its job. > > Make sure you store when you change something. Setting > cascading updates on Config may be the easiest way to ensure > that the HashMap is properly saved to the database, assuming > Config doesn't reference the rest of the WoT plugin. > >
