That was a tricky part, getting the selected or created value back to the original page. Perhaps it would have been better implemented with an event-driven approach, but I just went with what I could get working quickly. I'm sure I could come up with something more elegant if I had the time to ponder. :)
On Mon, Apr 4, 2011 at 1:08 PM, fernandospr <[email protected]> wrote: > Thanks James. I think I got it. > > I think the key part is this: > ((FooSelectionListener) page).fooSelected(foo); > > I guess "page" is the page that starts the loop and is waiting for a > selection, that is why it implements fooSelected. > > I think I'll implement something similar but instead of using a foo object > for fooSelected, I'll use an id. Then redirect to the original "page" and my > fooSelected would load it from the database. > > Though, I'm not sure if the original "page" would be automatically refreshed > with the selection. > > I will have to try. > > Thanks. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426075.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
