Ok, I got it:
- the buffer at once is serializable
- a attribut of the buffer (a repeated string) might be not
so I have to copy the UnmodifiableLazyStringList to an ArrayList if
I'd like to use the attribut as an argument to pass between beans.
Pro: I dont need to include protobuf.jar into all
Hi!
Most of the classes are already implementing Serializable. Maybe
UnmodifiableLazyStringList was just forgotten. I'll add Serializable
to this class and will try again. Maybe this simple thing is enough.
js
--
You received this message because you are subscribed to the Google Groups
"Proto
Also don't have enough Java-fu, but I'd thought this was basically how this
was solved: the messages override some function that cause the JavaVM to
serialize using protobuf serialization. I was under the impression that the
message internals would then no longer needed to implement Serializable.
On Wed, Apr 13, 2011 at 16:01, Ben Wright 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 "
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
Hi!
> Protocol buffers are objects to serialize things, but it doesn't
> really make sense to use Java serialization to serialize their holder
> objects.
I'd like to pass Java objects from a unserialized protocol buffer
between
Beans inside a application server. This makes sense to me.
> If you
