Hi Ivo, Thanks for digging around and identifying the potential culprit. I'm checking this out with John to see if this was a new change or existing behaviour that you somehow got around in 1.4.x.
In the meantime, could you refer us to the lines of code you traced this down to? After checking that out, it's possible that we'll have to log this as a bug in the Issue Tracker. Many thanks, -Sumit Chandel On Mon, Oct 20, 2008 at 9:39 AM, Ivo <[EMAIL PROTECTED]> wrote: > > Hi, > > While trimming down the application to a minimal testcase (which is of > course a form of debugging), > I found the culprit: a bit of caching in the Generator that prevented > the class from being generated > anew on a refresh, if it was already generated earlier on. That goes > to show that premature optimization > is once again the root of all evil. :) > > Has there been a change in behaviour here, causing generated classes > to be deleted and > regenerated on a refresh? Now that I think of it, I actually expect > the classes to be generated anew > and it may have been entirely coincidental that it worked in the first > place. > > Well, thanks for encouraging me to perform this bit of digging :) > > best regards, > -- > Ivo > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
