True that would fix the flush. But I'm wondering if this isn't a symptom of an earlier problem. I'm thinking if the list is null on instantiation the list backing doesn't get setup properly. So the question I would have is if I add an item, will the list no longer be null and it seems to me that it will still be null. So I think to fix the problem might be to instantiate the list differently as well.
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.
