On Wed, Apr 13, 2011 at 16:01, Ben Wright <compuware...@gmail.com> wrote:
> I agree with J.S. on this one - there are many situations in Java EE
> environments where "Serializable" is checked or java serialization
> used when it's not simple or feasible to leverage protobuf
> serialization.  Most of these situations are "invm / in memory"
> transfers.  Sometimes java serialization is used to clone objects or
> to safely pass them between ClassLoader scopes.
> I've run into this limitation with JBoss ESB and passing protocol
> buffer objects between services through the "InVM" message transport.

It is a couple of years that I've worked with Java, so my
serialization fu might not be up-to-par. But would the problem be
solved if the ProtocolBuffer object implements Externalizable ? That
way it can be serialized via the Java VM, but it would use the
protobuf specific serialization.


You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to