I just ran into this and I'm wondering why a ui:field is required? In our case, the object is self contained and after creation isn't referenced by the code that creates the object. Is this requirement really necessary?? I know the workaround is easy, its just that making us developers troubleshoot an error that seems to be a completely valid use case with very little info seems wrong. If nothing else maybe a better error message should be output?
On Monday, November 5, 2012 9:51:37 AM UTC-5, Thomas Broyer wrote: > Looking at the code for LazyPanelParser at line 40, it seems like you'd > have this exception if you do not have a @UiField for the LazyPanel in your > owner class. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
