I agree the hash exists,but I was looking for an option to actually put
data on the wire. Similar to the Java implemented WriteDelimeted functions
a WriteVersioned, such that the information is prepended. We can put the
information you listed in a message and prepend it ourselves. This works
hi,
This is actually a little more complicated than just version. There are
times I actually want to process with an old proto file and ignore new
fields added by some new development. This feature is one of the many that
made Protobuf attractive to our development needs. I think a better
I am working on a solution to basically allow me to persist any
protocol buffer with hibernate. However, I have run into a challenge
with nested builders. In order for hibernate to create relationships
it's requiring the parent object be referenced. For these purpose I
wanted the parent object
Well you can take in the language guide
http://code.google.com/apis/protocolbuffers/docs/proto.html#options
where it talks about custom options. It's just below the Options
section. This shows how to do it for a message and you'll be using
the FieldDescriptor to do this. One more thing to note
Well you can take in the language guide
http://code.google.com/apis/protocolbuffers/docs/proto.html#options
where it talks about custom options. It's just below the Options
section. This shows how to do it for a message and you'll be using
the FieldDescriptor to do this. One more thing to note
Marco,
Short answer is I haven't seen one, but what exactly are you trying to
do? I struggle to understand why you would need this capability.
You might check out Protostuff - they have a POJO to Protobuf
capability.
Regards,
Mike
On May 20, 11:18 am, Marco Tedone marco.ted...@gmail.com
For using existing pojos you can look at the protostuff project.
On Mar 18, 12:53 pm, Christopher Smith cbsm...@gmail.com wrote:
Are these POJO's or object generated by protoc? If the former, I would say
you are SOL. If the latter, you can ask the object for its descriptors and
actually dump
One other thing to consider (if performance is not an issue) is to
extend Smooks (www.smooks.org). I have been considering this my self
although currently I do not have enough of a need to write this yet.
Basically you would write the Smooks cartridge to read a PB. You
can throw SAX events in
have realized enumeration changes may be
particular difficult to adapt to with compatibility issues. Can you
point to any strategies here?
Thank you for all the input and advice!
On Sep 21, 3:38 pm, Kenton Varda ken...@google.com wrote:
On Wed, Sep 15, 2010 at 6:03 AM, users moofis
I am implementing PB to provide an external interface and API to a
developing system. I know the interface will change and the extension/
backwards compatibility is a major benefit. When designing the .proto
files should I, for pure flexibility, make everything optional or
repeated fields? If I
Have you tried putting the import path in quotes?
import foo.proto
Second ... The import function needs a path, not the dot notation.
import com/foo/bar/some.proto might work?
On Sep 9, 9:26 am, jebrick jebr...@gmail.com wrote:
I want to import 2 files to my proto for compiling.
The
Eugene,
I am in the exploration process of using Protobuf's with a project.
For my level integration I took all the Java Google code and created a
Plug-in Project in Eclipse RCP. Then using the export feature (OSGi)
I reference the necessary code. I think you might be integrating the
Protobuf
So at various times (2008 - 2009) there are posts by people inquiring
about conversions from XML Schemas to .proto.
Even one such post provided the xslt file. Is there any chance the
Protocol Buffer project will formally support and release an XSLT that
would be updated with each release? Would
13 matches
Mail list logo
