[jira] Commented: (DIRMINA-161) A ObjectSerializationEncoder that works with Java's ObjectInputStream.readObject()

["Trustin Lee (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/DIRMINA-161?page=comments#action_12362576 ] 

Trustin Lee commented on DIRMINA-161:
-------------------------------------

It would be nice if we can, but it takes a lot of energy to fulfill it.  We'll have to analyze the object stream so we can find out when it ends.  Moreover, this will break when Sun adds something to the protocol.  That's why we used the header data which represents the length of the serialized object.

What do you think about providing object input/output stream classes that can read/write the stream that MINA wrote?

> A ObjectSerializationEncoder that works with Java's ObjectInputStream.readObject()
> ----------------------------------------------------------------------------------
>
>          Key: DIRMINA-161
>          URL: http://issues.apache.org/jira/browse/DIRMINA-161
>      Project: Directory MINA
>         Type: New Feature
>     Versions: 0.9
>     Reporter: Andy Korth
>     Priority: Minor

>
> Having a class similar to ObjectSerializationDecoder/Encoder that was compatable with ObjectInputStream.readObject() would be very helpful for those who are rewriting servers to use MINA without the ability to change client code.
> Currently, an attempt to use readObject() to receive information from the existing ObjectSerializationEncoder results in:
>  org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.mina.common.BufferDataException: dataLength: -1393754107 (Hexdump: empty)
> I suspect this has something to do with the reading of the prefixed data.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira