For starters I'd try a BookmarkablePageLink instead of a Link. If that
doesn't work, I recommend reproducing the issue in a simple quick start (
http://wicket.apache.org/start/quickstart.html) and posting the the users
list ([email protected]). It has a wider audience for helping on
issues like this.

Regards,
Dan

On Wed, Sep 21, 2011 at 2:44 PM, Henry, Mike [GCG-PFS] <
[email protected]> wrote:

> Here is my code but still not working. Thanks for the help.
>
> Link print = new Link("printLink2"){
>
>                        /**
>                         *
>                         */
>                        private static final long serialVersionUID = 1L;
>
>                        @Override
>                        public void onClick() {
>                                setResponsePage(FnaPrintPage.class);
>
>                        }
>
>                };
>                print.setPopupSettings(new PopupSettings(PageMap
>                                .forName("popupPageMap"),
> PopupSettings.RESIZABLE
>                                |
> PopupSettings.SCROLLBARS).setHeight(768)
>                                .setWidth(1024));
>
>
> Mike Henry
>
> 770-564-7863
> Offsite Wednesday and Friday
> Cell 404-295-6094
>
> -----Original Message-----
> From: Dan Retzlaff [mailto:[email protected]]
> Sent: Wednesday, September 21, 2011 5:33 PM
> To: [email protected]
> Subject: Re: 2nd wicket browser window hoses first
>
> This issue may exceed my expertise to debug without a quick start.
> Sorry. :)
>
> To answer your question, you can call isVersioned() on your page, but
> you'd probably know if you overrode the default of true.
>
> On Wed, Sep 21, 2011 at 2:25 PM, Henry, Mike [GCG-PFS] <
> [email protected]> wrote:
>
> > We have this in our init in WicketApplication.java
> > get().getPageSettings().setAutomaticMultiWindowSupport( true );
> >
> > How/where do I check versioning?
> > Thanks
> >
> >
> > Mike Henry
> >
> > 770-564-7863
> > Offsite Wednesday and Friday
> > Cell 404-295-6094
> >
> > -----Original Message-----
> > From: Dan Retzlaff [mailto:[email protected]]
> > Sent: Wednesday, September 21, 2011 5:22 PM
> > To: [email protected]
> > Subject: Re: 2nd wicket browser window hoses first
> >
> > Yes it is true by default, until SecondLevelCacheSessionStore (the
> > default) sets it to false. Forcing back to true in your
> > Application.init() should fix the issue. Alternatively, I think think
> > the preferred solution is to use PopupSettings on the link. This tells
>
> > Wicket in advance that the new page should have its own page map, and
> > automatically adds target="_<pagemapname>"
> > to the markup IIRC.
> >
> > I still suspect that you've disabled versioning, though, since
> > component hierarchy changes should increment the page version and
> > leave the original intact. At least that's my understanding.
> >
> > On Wed, Sep 21, 2011 at 2:13 PM, Henry, Mike [GCG-PFS] <
> > [email protected]> wrote:
> >
> > > Dan
> > > Thanks for the reply. The new browser window is opened on the link
> > > with target="_blank".
> > > <a hef="#" wicket:id="printLink2" target="_blank">
> > >                            Print
> > >                         </a>
> > >
> > > The print link goes to a new wicket page and as soon as it loads the
>
> > > first window no longer works. I will check the value of that
> > > property it said in the javadoc that it was set to true by default.
> > >
> > >
> > > Mike Henry
> > >
> > > 770-564-7863
> > > Offsite Wednesday and Friday
> > > Cell 404-295-6094
> > >
> > > -----Original Message-----
> > > From: Dan Retzlaff [mailto:[email protected]]
> > > Sent: Wednesday, September 21, 2011 5:06 PM
> > > To: [email protected]
> > > Subject: Re: 2nd wicket browser window hoses first
> > >
> > > 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
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
> >
>
>

Reply via email to