Closed kul closed 9 years ago
Hi kul, is this still an issue or did you find a resolution?
Hi, I ended up sticking to 1.5.1 for data freezed with 1.5.1. I think this should still be reproducible.
:nippy/unthawable
errors are thrown when the class (in this case org.Dummy
) cannot be created through the Serializable implementation that you've provided:
(cast (Class/forName "org.Dummy") (.readObject <as-serialized>))
I don't use it myself so I'm not familiar with Java's Serializable and its portability characteristics. If the docs are no help, I'd suggest using Nippy's extend-freeze
, extend-thaw
to specify a stable binary representation for your type that doesn't depend on Serializable.
Hope that helps, cheers! :-)
I have the following java class as an example, in a project lets say org.foo/dummy-project
Now if the above dependency is available in two clojure projects with nippy 2.6.2 and clojure 1.5.1 and 1.6.0 respectively. The following errors are encountered
From 1.5.1 project
From 1.6.0 project
I noticed that this happened after introduction of the Keyword member in Dummy class.