Using Other Message Types using import - message is not defined

Hi, I have to proto files ADMObjectHandleMessage.proto and AbstractADMAdapterMessage.proto: ADMObjectHandleMessage.proto == package com.qnamic.base.agent; message ADMObjectHandle { optional string host = 1; optional string agent = 2; optional string

Re: Using Other Message Types using import - message is not defined

Ok. I forgot to the type the full qualified name including package: required com.qnamic.base.agent.ADMObjectHandle objectHandle = 1; Tai On 4 Aug., 12:14, Tai maitai.tru...@gmail.com wrote: Hi, I have to proto files ADMObjectHandleMessage.proto and AbstractADMAdapterMessage.proto:

java class name different from proto file name

I got a strange behaviour when compiling a protofile (e.g. MyClass.proto). The generated java class is then called MyClassProto. All other proto files works fine. As a workaround I have added the following line to the proto file: option java_outer_classname = MyClass; Any idea what I am doing

Re: java class name different from proto file name

Are you using Windows by any chance? On Aug 4, 11:54 am, Tai maitai.tru...@gmail.com wrote: I got a strange behaviour when compiling a protofile (e.g. MyClass.proto). The generated java class is then called MyClassProto. All other proto files works fine. As a workaround I have added the

Re: java class name different from proto file name

Yes, I am using Windows XP and Eclipse 3.5 On 4 Aug., 19:49, Stefan sneg...@gmail.com wrote: Are you using Windows by any chance? On Aug 4, 11:54 am, Tai maitai.tru...@gmail.com wrote: I got a strange behaviour when compiling a protofile (e.g. MyClass.proto). The generated java class is

Re: java class name different from proto file name

What it is also funny is that my file ADMObjectHandleMessage.proto looks like this: package com.qnamic.base.agent; option java_outer_classname = ADMObjectHandleMessage; message ADMObjectHandle { optional string host = 1; optional string agent = 2; optional string path = 3;

Re: java class name different from proto file name

Thanks. Your were pointing into the right direction. It wasn't the filename but the compile argument when using ant: project name=Create PB classes default=generate basedir=../../../.. target name=generate exec executable=D:/development/workspace/Platform/dev/jars/ protoc

Changing {parse,merge}DelimitedFrom()

In Java I introduced methods called writeDelimitedTo(), parseDelimitedFrom(), and mergeDelimitedFrom() in version 2.1.0. These read and write messages which are prefixed with the message size, thus allowing multiple messages to be written to one stream without any external delimiter. As one or

'Search this group' isn't very helpful

I'm finding that the search function provided by the group is returning much less than I expect. Is anyone else having similar trouble? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post

Re: 'Search this group' isn't very helpful

What were you searching for? Are you sure there should be results? On Tue, Aug 4, 2009 at 3:07 PM, yellen yel...@gmail.com wrote: I'm finding that the search function provided by the group is returning much less than I expect. Is anyone else having similar trouble?

Re: 'Search this group' isn't very helpful

On Aug 4, 5:16 pm, Kenton Varda ken...@google.com wrote: What were you searching for?  Are you sure there should be results? I originally searched for 'rpc' which I'm pretty sure in the past brought up over 3 pages of results. I've been archiving the emails locally from the group for over a

Re: java class name different from proto file name

Yes, that's correct. If the Win32 API strips trailing whitespace from file names when opening them, that would explain why there was no error -- but that's very strange behavior IMO. On Tue, Aug 4, 2009 at 4:26 PM, Tai maitai.tru...@gmail.com wrote: This could be a windows problem where white

Re: 'Search this group' isn't very helpful

Interesting. I'll file a bug against google groups. On Tue, Aug 4, 2009 at 3:25 PM, Adam yel...@gmail.com wrote: On Aug 4, 5:16 pm, Kenton Varda ken...@google.com wrote: What were you searching for? Are you sure there should be results? I originally searched for 'rpc' which I'm pretty

list member containing sub classes

Hi, I have an (abstract) class: - OParameter with a member String key Now there are also two subclasses of OParameter: - OStringParameter with a member String value - OLongParameter with a member long value By using Protocol Buffers I define the proto files: - OParameterMessage.proto -

Re: java class name different from proto file name

That's not strange. That's a Windows feature :-) On 5 Aug., 01:50, Kenton Varda ken...@google.com wrote: Yes, that's correct.  If the Win32 API strips trailing whitespace from file names when opening them, that would explain why there was no error -- but that's very strange behavior IMO. On

Re: list member containing sub classes

Can you just have the OParameter message contain optional fields of type string and int64, where only one of the two is ever set? Then don't have specific types corresponding to OStringParameter and OLongParameter. On Tue, Aug 4, 2009 at 5:07 PM, Tai maitai.tru...@gmail.com wrote: Hi, I