That is a page with a form right?
The youre controller logic lies the the onSubmit of the search button or the onSubmit of the form itself.
Don't think in servlets. Think in components and actions.
On 13 Sep 2005 15:47:00 +0200, Voors Paul <[EMAIL PROTECTED]> wrote:
Hello Wicket Users,
After examining the documentation and examples for some time, i am missing one aspect in Wicket. That is a 'Central Controller'. Let me explain:
If a user sends a request -for instance a search request for something- the/my application should be able to return different pages based on the results. Normally this is done in a controller(servlet). Within Wicket I don't now how to this in a proper way.
The (web)application class seems to be the central point of the application, but i don't see how to do the trick in this class. I could use a page (class) for it, but a page is not the right class for such control/logic (to my opinion).
Can anyone gife me a suggestion?
Paul Voors
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
