Hi,
On Fri, Feb 12, 2016 at 3:34 PM, Aaron J. Garcia wrote:
> Aaron J. Garcia rentec.com> writes:
>
> >
> > Hi Martin & Sven,
> >
> > Thanks for your replies!
> >
> > I ended up sending getPage().getPageId(). Is the better practice to use
> a
> > PageReference? If so, I'll change my code to
Aaron J. Garcia rentec.com> writes:
>
> Hi Martin & Sven,
>
> Thanks for your replies!
>
> I ended up sending getPage().getPageId(). Is the better practice to use a
> PageReference? If so, I'll change my code to use that instead.
>
> Secondly, I had no idea that you could use a Panel for th
Hi Martin & Sven,
Thanks for your replies!
I ended up sending getPage().getPageId(). Is the better practice to use a
PageReference? If so, I'll change my code to use that instead.
Secondly, I had no idea that you could use a Panel for the contents of a
ModalWindow. I always thought you needed
Hi,
> to pass a message from the content of my ModalWindow back to the
ModalWindow itself
why would you want to do that? Your ModalWindow is part of another page,
so it cannot update itself in the same request.
> getPage().getParent() returns null. Is there a reason for this?
Each page ins
Hi,
It is a bad practice to keep references from one page to another.
Keeping reference means that serializing any of the pages will serialize
the other too.
For that reason there is PageReference class. You could use it to keep a
"weak" reference to another page. It keeps just the page id, so it
Hi Everyone,
ModalWindow has a "setPageCreator()" method, to set the page that you want
to display inside of the ModalWindow.
I've never used Wicket's event infrastructure, but I decided to use it today
to pass a message from the content of my ModalWindow back to the ModalWindow
itself.
Apparent
