Nobody responded but I realize I didn't really give much to go on but I was able to get my data to come up.
I had multiple issues. The first was that, for some reason, when I compiled my JS output it wasn't completely correct (it didn't recognize my binary flag I guess) so recompiling it gave me access to the deserializeBytes function. The other issue was I was using the Sproutcore framework's XHR Response that would somehow lose my bytes (about 300KB) somewhere along the line. Switching to pure Javascript XHR fixed that issue as well. On Tuesday, December 13, 2016 at 8:27:44 AM UTC-6, Joseph Middleton wrote: > > Hello everyone, > > I'm new to using protocol buffers and think I've gotten stuck where I'm > at. I'm currently trying to send a message that has other messages embedded > in it which can have other messages embedded in it. I'm sending this > message via REST request (application/octet-stream) but when I try to run a > toObject method (using the generated Javascript) on the response all of the > objects come back as "undefined" within the larger object. > > On the server side of things (Java), when I look in the debugger, I'm > assuming I'm sending it up correctly but am not really sure. > > Sorry if this is really vague. I suppose I need guidance on what my > problem is. > > Thanks! > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
