Added the new method to IPageManager in 7.x and to AbstractPageManager in 6.x.
Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Jul 7, 2015 at 9:47 PM, Martin Grigorov <[email protected]> wrote: > The new untouch() most likely will be in IPageManager, an interface, so it > has to be added before 7.0.0. > I'll do it shortly. > > Additionally we have to fix the issue with #getResourseStream() before > 7.0.0. > I'll do it shortly too. > > In the meantime you may test your apps against current master to avoid > more restarts of the release. > On Jul 7, 2015 9:15 PM, "Andrea Del Bene" <[email protected]> wrote: > >> I meant to go ahead with a new build without this change. >> >>> I vote -1 for the release. The effects caused by the change were very >>> easy >>> to reproduce, and I know our applications are very likely to be affected. >>> We heavily rely on pages in page store to implement 'cancel' and 'return' >>> buttons in our applications. We also use ajax extensively and often >>> update >>> properties that will not cause the page to become dirty. This will >>> undoubtedly lead to subtle bugs and inconsistent behavior. >>> >>> Also, the proposed API change seems quite important to me. This has to be >>> changed before 7.0.0, or else it will have to wait until 8.0.0. >>> >>> Best regards, >>> Emond >>> >>> On Tue, Jul 7, 2015 at 5:59 PM, Andrea Del Bene <[email protected]> >>> wrote: >>> >>> I've reverted the commit for this issue. Since this issue doesn't seem >>>> to >>>> affect many people I suggest to go ahead with the release and postpone a >>>> possible extension of the API to untouch a page. In the meantime to >>>> solve >>>> the problem of the issue we could suggest to use a stateless page, which >>>> might use stateless AJAX components from WicketStuff. >>>> >>>> Andrea. >>>> >>>> >>
