Im struggling to find a way of creating a generic Transaction packet, that 
can encapsulate many transaction types. I was doing this with oneof but 
oneof cannot be extended. Enums can't be extended either. 

Im lost at this point for how to let one or more clients extend Transaction 
and have their own wrapped classes that all get built in the end.

Any advice would be welcome. 

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to