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. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
