[DIRMINA-627] ByteBuffer.getObject() doesn't support Class objects for non-serializable classes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.7
• Fix Version/s: 2.0.3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Owen Jacobson
• Created: 03/Oct/08 03:39
• Updated: 30/Aug/11 08:40
• Resolved: 17/Mar/11 23:01

Description

Instances of java.lang.Class are serializable, whether or not the class they represent is serializable. However, org.apache.mina.common.ByteBuffer's optimizations prevent it from unserializing Class instances representing classes that are not serializable. For example, given

public interface NotSerializable {}
/.../
ObjectOutputStream o = /.../;
o.writeObject (NotSerializable.class);
/.../
ObjectInputStream i = /..bytes written by o, above../;
Object read = i.readObject();

The 'read' object will be NotSerializable.class.

Trying the same thing with buffer.putObject (NotSerializable.class); buffer.flip(); buffer.getObject() throws a NullPointerException.