Thats a good point and as soon as I posted that I wondered that my self. The first thing I'd like to do is pause on it and see which of my list editors has a null list because the list editor wants an empty or greater list. But pausing on every list is tiresome and would rather pause on an exception. Better yet, the next thing I was wondering is either add an assertion to the editor saying the list can't be null or add a better trace for the list NPE, saying something like PeopleListEditor can't be null.
The way I find them now is make sure any lists on the server side when null send an empty. Have a good day, Brandon Donnelson +Follow Me <https://plus.google.com/u/0/111739836936169749229/posts> On Thu, May 17, 2012 at 3:19 AM, Thomas Broyer <[email protected]> wrote: > > > On Thursday, May 17, 2012 2:31:17 AM UTC+2, Brandon Donnelson wrote: >> >> How about put a try catch around the list.flush() for tracking down the >> offending null list. >> >> ListEditor.class { >> //... >> public void flush() { >> list.flush(); // <<<< try catch this for easier debugging >> } >> //... >> } >> >> Thoughts? >> > > What would the "catch" block do? > > Wouldn't the correct fix rather be: if (list != null) { list.flush(); } > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/j72sBQj23r8J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
