Well, I think I earned my cleverness points for today, if I do say so myself.
By moving the writing of the datastore into a different class, I have managed to prevent Kaffe from crashing when reading a JDK-generated datastore. It still can't load a datastore under Kaffe, but at least it doesn't crash. Oh, I also reduced the amount of stuff within the synchronized(), for what it's worth. The reason I went down this path is that I theorized that Kaffe was getting unhappy trying to load a datastore when the store was trying to load a class with an open file (namely, the file containing the datastore). Maybe my theory is all whacked out, but who knows. I do feel the suggestion to write the datastore out in a JVM-independent format is a good one. Now, if someone could magically come up with such a format... _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
