BTW, I don't know what could cause a stack trace to be null. Are you
catching the exception somewhere and then replacing the stack trace?
On Mon, Nov 23, 2009 at 6:55 PM, Kenton Varda <ken...@google.com> wrote:
> Is it possible that you passed a different --proto_path when you were
> compiling Issuer.proto, Subject.proto, or Conditions.proto than you did when
> compiling Assertion.proto? You need to make sure you pass the same
> proto_path in all cases. (The default proto_path is the current directory,
> so if you don't specify a path, you must run all compilations from the same
> directory.)
>
>
> On Mon, Nov 23, 2009 at 6:46 PM, <suja...@gmail.com> wrote:
>
>> Sorry, forgot to mention. I am using Java. This started failing after
>> having to regenerate the code since one of the dependent classes changed.
>>
>> Here is the exception details.
>> java.lang.IllegalArgumentException: Invalid embedded descriptor for
>> "Assertion.proto"
>>
>> message
>> com.google.protobuf.Descriptors$DescriptorValidationException:
>> Assertion.proto: Dependencies passed to FileDescriptor.buildFrom() don't
>> match those listed in the FileDescriptorProto.
>>
>> stacktrace is null
>>
>> proto DescriptorProtos$FileDescriptorProto (id=1338) has the following in
>> debug
>>
>> name: "Assertion.proto"
>> dependency: "Issuer.proto"
>> dependency: "Subject.proto"
>> dependency: "Conditions.proto"
>>
>> I can't see any variable associated with fieldDEscriptor but from the code
>> i can see FieldDescriptor as follows
>> com.google.protobuf.Descriptors.FileDescriptor
>> .internalBuildGeneratedFileFrom(descriptorData,
>> new com.google.protobuf.Descriptors.FileDescriptor[] {
>> com.ebay.idp.proto.IssuerProto.getDescriptor(),
>> com.ebay.idp.proto.SubjectProto.getDescriptor(),
>> com.ebay.idp.proto.ConditionsProto.getDescriptor(),
>> }, assigner);
>>
>> sujata
>>
>>
>>
>>
>>
>> On Nov 23, 2009 6:15pm, Kenton Varda <ken...@google.com> wrote:
>> > Need more information:- What language are you using?
>> > - What is the full error message and stack trace?
>> >
>> > On Mon, Nov 23, 2009 at 6:01 PM, suja...@gmail.com suja...@gmail.com>
>> wrote:
>> >
>> >
>> > I get the following error on initialization of one of My protos. as
>> >
>> > far as I can tell the dependedncies are all correct but the the
>> >
>> > initialization code seems to find differences between
>> >
>> > FieldDescriptorProto and FieldDescriptor and gives me the following
>> >
>> > error.
>> >
>> > "Invalid embedded descriptor for"
>> >
>> >
>> >
>> > was hoping someone can explain what is going on.
>> >
>> > thx
>> >
>> > sujata
>> >
>> >
>> >
>> > --
>> >
>> >
>> >
>> > You received this message because you are subscribed to the Google
>> Groups "Protocol Buffers" group.
>> >
>> > To post to this group, send email to proto...@googlegroups.com.
>> >
>> > To unsubscribe from this group, send email to
>> protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
>> .
>> >
>> > For more options, visit this group at
>> http://groups.google.com/group/protobuf?hl=en.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@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.
