Hello Ryan,
this happens when the object deserialization fails with either
IOException or ClassNotFoundException. It can also happen when "data
instanceof ByteBuffer" reports false which would be a class loader issue.
Pavel
On 18.6.2013 22:30, Ryan Cuprak wrote:
Just curious if anyone has ever run into a situation where you get a
java.nio.HeapByteBuffer instead of the deserialized object? I implemented drag
and drop in a table in a TableView. It works fine in the test app but fails in
the actual application - drop gets receives the HeapByteBuffer instead.
Thanks,
-Ryan
