On Mon, Jun 13, 2011 at 11:28 PM, Yanni Chiu <yanni@rogers.com> wrote:
In my test case for serializing a Pier kernel with Fuel, a FSMemoryStore (from the FileSystem package) is used.
I really didn't understand, sorry :( Why the following is not enought? (FLSerializer on: myStream) serialize: myPRKernel. and (FLMaterializer on: myStream) materialize
The FSMemoryStore holds the "file" bytes in a ByteArray. During serialization, I got a stack trace with KeyNotFound due to FLSerializer>>nextPutReferenceTo: when the object is the "file" ByteArray.
Since this ByteArray is where the serialization is being written to,
mmmmmm so you are using a stream to serialize and such stream is also being refenced from the object to serialize?
then it's hash value is changing, so Fuel serialization cannot find it in the instancesIndex.
I think this is expected behaviour, and the fix is to not serialize certain inst vars. I was using the "stable" 1.4 version. Do I need to change to the 1.5 baseline to get the #fuelIgnoredInstanceVariableNames feature?
-- Yanni
-- Mariano http://marianopeck.wordpress.com