[protobuf] Re: Issue 205 in protobuf: Invalid strings are delivered to application

2012-05-31 Thread protobuf


Comment #4 on issue 205 by hamel.st...@gmail.com: Invalid strings are  
delivered to application

http://code.google.com/p/protobuf/issues/detail?id=205

It would help if the warning (in debug mode) also printed the message type  
name.


--
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.



[protobuf] Protobuf and entity framework - included entities serialization

2012-05-31 Thread ADE
Hi all,
I am not able to serialize nested entities.

This is my transfer object

[ProtoContract]
[Serializable]
[DataContract]
public class MyClassTO
{
[ProtoMember(1)]
[DataMember]
public ListMyEntity ListOfMyEntities {get;set;};

}

On my backend, I fire the following linq to entities query, fill the
transfer object and return it to the client:

var myClassTO  = new MyClassTO();

myClassTO.ListOfMyEntities =
Context.MyEntity.Include(ReferencedEntity.AnotherReferencedEntity).ToList;

return myClassTO;

The client receives the list of MyEntity objects but included entities
are not serialized(they are all null). Does anybody have any idea
about it?

-- 
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.



[protobuf] Re: Issue 351 in protobuf: Make protobuf_lite proto files not create any static initializers

2012-05-31 Thread protobuf


Comment #9 on issue 351 by tha...@chromium.org: Make protobuf_lite proto  
files not create any static initializers

http://code.google.com/p/protobuf/issues/detail?id=351

Fixed, right?

--
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.



[protobuf] Issue 393 in protobuf: Allow configure to disable maintainer mode

2012-05-31 Thread protobuf

Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium

New issue 393 by robnap...@gmail.com: Allow configure to disable maintainer  
mode

http://code.google.com/p/protobuf/issues/detail?id=393

Currently protobuf does not support disabling automake's maintainer mode.  
In maintainer mode, the configure script can be rebuilt if it appears to  
be older than its dependencies. This is good for maintainers, but plays  
havoc for downstream packagers who checkin the contents of the tarball.  
Many version control systems do not maintain file dates, so configure can  
look stale and may be rebuilt when it should not be. If configure is  
readonly (such as when stored under Perforce), the build will fail.


The solution is adding AM_MAINTAINER_MODE([enable]) to configure.ac. This  
changes nothing by default, but adds the configure option  
--disable-maintainer-mode, which tells configure never to rebuild itself  
even if its dates appear incorrect.


Attachments:
protobuf-maintainermode.patch  547 bytes

--
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.