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 spaces are accepted when > doing a file lookup. I further assume when protoc takes the argument > it uses the filename including the white space to generate the class > name. Maybe that was the reason why the class was called > "MyClassProto" and not "MyClass". > > Tai > > On 4 Aug., 23:19, Kenton Varda <ken...@google.com> wrote: > > In that case I'm surprised it compiled -- I would have expected protoc to > > report "file not found". Weird. > > > > On Tue, Aug 4, 2009 at 2:16 PM, Tai <maitai.tru...@gmail.com> wrote: > > > > > 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"> > > > <arg > value="-I=Platform/dev/config/protocolbuffers" > > > /> > > > <arg value="--java_out=Platform/src" /> > > > <arg value="Platform/dev/config/protocolbuffers/ > > > ADMObjectHandleMessage.proto" /> > > > <arg value="Platform/dev/config/protocolbuffers/ > > > ADMTimeMessage.proto" /> > > > </exec> > > > </target> > > > </project> > > > > > The argument was: > > > value="Platform/dev/config/protocolbuffers/ > > > ADMObjectHandleMessage.proto " > > > and not: > > > value="Platform/dev/config/protocolbuffers/ > > > ADMObjectHandleMessage.proto" > > > > > Tai > > > > > On 4 Aug., 22:12, Kenton Varda <ken...@google.com> wrote: > > > > It looks like your problem is that your file name actually has a > space > > > > tacked on to the end of it. That is, the name is "MyClass.proto " <- > > > note > > > > the last space. You should get rid of that space. > > > > > > On Tue, Aug 4, 2009 at 9: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 > > > > > following line to the proto file: > > > > > > > option java_outer_classname = "MyClass"; > > > > > > > Any idea what I am doing wrong? > > > > > > > Thanks Tai > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---