On Wed, Dec 21, 2011 at 12:45 AM, Brian Slesinsky <[email protected]> wrote: > On Tue, Dec 20, 2011 at 2:36 PM, <[email protected]> wrote: > >> On second thought, even though List and Set are the two that are >> technically allowed, there's really no problem with JSON-RPC and the >> encoding of a Collection, as its done in the exact same way regardless >> of the collection; I don't think it hurts us to be a bit loose here. >> What do you think? > > I'm leaning towards being more restrictive until someone asks for it, > since it's easier to relax a restriction than to tighten it up. Most > of the time people will be writing AutoBeans interfaces from scratch > and they should probably stick to using maps and lists since that's > what JSON and JavaScript support directly, so it will be the most > efficient in GWT. > > But I haven't figured out this code and this isn't a public method. Do > we check for this somewhere else? Maybe some unit tests would make it > more clear.
cloneBeanAndCollections checks for Set/List vs. other Collection-type on RequestContext#edit() (or when passing a non-edited proxy as argument to a context/service method), and AutoBeanCodexImpl.CoderCreator does the check on setting a property on any AutoBean (which RF proxies are). -- Thomas Broyer /tɔ.ma.bʁwa.je/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
