Answering my own questions.
I can also pass the search panel to the results page from my form onSubmit:
setResponsePage(new SearchResults(((PanelSearch)this.getParent()),
search));
Then, in the results page:
public SearchResults(PanelSearch searchPanel, Search search) {
add(searchPanel);
}
Mostly seems to work OK - panel on results page retains state from search
page.
Still getting some weird behaviour with the Ajax dropdowns on page refreshes
- can get crazy state of North America, Canada, Kansas if I refresh the page
between selection changes (old state gets mixed in with partial new state)
Other thing to sort is how to reload panel state if user goes back to the
home page (containing search panel) via a basic external navigation link -
panel will be in its initial blank state. Perhaps I do need to look into
loading from the session for this.
But I'm starting to like Wicket - this kind of stuff takes much more code in
other frameworks.
steviezz wrote:
>
> I am now passing the search form model to the new page in the constructor,
>
> setResponsePage(new SearchResults(search));
>
> Works OK - I assume this is better than going through the session.
>
> But I have no idea (yet) how to reinitialise the search panel Ajax
> widgets.
>
>
>
>
> wicket user-2 wrote:
>>
>> store the backing model in the session and get it from the session, this
>> will help you retain the state in all the cases
>>
>> Cheers
>> Dipu
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Combining-Ajax-and-non-Ajax-pages-tp15587166p15607263.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
