Actually IPageSettings.setAutomaticMultiWindowSupport isn't necessarily true by default. You should check what your value is.
On Wed, Sep 21, 2011 at 2:03 PM, Dan Retzlaff <[email protected]> wrote: > With IPageSettings.setAutomaticMultiWindowSupport(true), the default, > Wicket tries to detect new tabs/windows and creates a new page map for them. > Modifications in the new page map should not affect the original. Even if > that detection fails, the worst I'd expect is page expiration exceptions, > not component not found. Which leads me to ask whether the page in question > is versioned at all? Are you just shift-clicking a link to open a new > window, or are you using PopupSettings? > > Dan > > > On Wed, Sep 21, 2011 at 1:41 PM, Henry, Mike [GCG-PFS] < > [email protected]> wrote: > >> I open a new browser window from a link on a wicket page which contains >> another wicket page. When I go back to the first page all the links >> throw component not found on page. Does wicket not support multiple >> browser windows? Is there a setting or way to handle this? >> Thanks >> >> Mike Henry >> >> >> >
