This is the way we do it. But I'll leave the expert respond to that :) On Sun, Jun 22, 2008 at 8:53 PM, Serkan Camurcuoglu <[EMAIL PROTECTED]> wrote:
> Hi all, > I'm quite new to Wicket and I'd like to ask whether what I'm doing is > right. Say I have two pages A and B. Page A loads a list of information from > the database and keeps it in an instance field. When a link on page A is > clicked, a new page B is created and page A passes itself as one of the > constructor arguments of B. Page B displays the information and includes a > link at the bottom saying "Back". When this link is clicked, Page B calls > setResponsePage() using the instance of Page A that was passed in its > constructor, and Page A is displayed again. > > That way I believe that I avoid reloading the data from the database again > in Page A. > > But I think somewhere in the mail archives I've read that it's recommended > to use setResponsePage(Class) instead of using setResponsePage(Page). So I'm > wondering whether I'm doing it right, and if there is a better way I'd like > to learn it. > > Sorry if this is a dumb question but I want to be confident about what I'm > developing.. > > Regards, > > SerkanC > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Eyal Golan [EMAIL PROTECTED] Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74
