only the:
public void detach(RequestCycle requestCycle)
{
if (page != null)
{
page.internalDetach();
}
}
of a RequestTarget does it.
But before that we do session.touch(page)
and with a second level cache. We will save that page then. We now do there quickly:
// TODO check can this be called everytime at this place? Putting should
// be called after the rendering so it should be ok.
page.detachModels();
(and this call is now changed to page.internalDetach())
but this brings the question why arent we do this earlier?
Why does page.renderPage() an internalAttach() call but not at the and internalDetach()?
I know we still have to do it in the request cycle because it can be a RequestTarget that is only used for handling the event.
And not processing the response (so the page is not rendered)
Can't we streamline this a bit more?
What we also could do is call session.touch() in the page.internalDetach()
but don't know what the result of that would be for that because then touch can be called on a event page not a response page.
But i guess this should be done anyway because if the event page is called on and some changed then we don't record this.
because it isn't touched?
johan
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
