Some of the classes are not supposed to be persistent. Of course you can avoid saving their instances in your code and mark all their occurrences in another classes as transient (Java/.NET). But that needs some attention and additional coding. You can achieve the same result in an easier way using TransientClass interface:
Java:
com.db4o.types.TransientClass
TransientClass is a marker interface, which guarantees that the classes implementing it will never be added to the class metadata. In fact they are just skipped silently by db4o persistence mechanism.
An example of the TransientClass implementation is db4o object container (we do not need to save a database into itself).
Let's look how it works on an example. We will create a simplest class implementing TransientClass interface:
01/* Copyright (C) 2004 - 2006 db4objects Inc. http://www.db4o.com */ 02
03
package com.db4odoc.selpersist; 04
05
import com.db4o.types.TransientClass; 06
07
08
public class NotStorable implements TransientClass { 09
10
public String toString(){ 11
return "NotStorable class"; 12
} 13
}
NotStorable class will be used as a field in two test objects: Test1 and Test2.
In our example we will use the default configuration and save Test1 and Test2 objects just as usual:
01public static void saveObjects(){ 02
new File(YAPFILENAME).delete(); 03
ObjectContainer oc = Db4o.openFile(YAPFILENAME); 04
try 05
{ 06
Test1 test1 = new Test1("Test1", new NotStorable()); 07
oc.set(test1); 08
Test2 test2 = new Test2("Test2", new NotStorable(), test1); 09
oc.set(test2); 10
} 11
finally 12
{ 13
oc.close(); 14
} 15
}
Now let's try to retrieve the saved objects:
01public static void retrieveObjects() 02
{ 03
ObjectContainer oc = Db4o.openFile(YAPFILENAME); 04
try 05
{ 06
ObjectSet result = oc.get(null); 07
listResult(result); 08
} 09
finally 10
{ 11
oc.close(); 12
} 13
}