Hi I'd like to integrate Wicket into an existing web application. That means a part of the web page should be done Wicket. Similar to a portlet, except that I don't use JSR-186.
The application is structured in a chain of servlet filters. Ideally I'd able to split the callback processing in a different filter than the rendering. This way I can be sure that the response is not yet committed and I can do a redirect in callbacks if I feel like it. My envisioned setup looks something like this: - ... other filters ... - MyWicketCallbackFilter * figure out the application from the request * process callbacks * if redirect then redirect and stop * else delegate to next filter - ... other filters ... - ... rendering starts here ... - MyWicketRenderingFilter * let application from above render * Maybe also add headers * delegate to next filter - ... maybe some more rendering ... Ideally I'd also be able to configure the URL generation of Wicket. That means mostly prefixes for the path. Does this make sense? Is this feasible? Do you have any pointers for me? Cheers Philippe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
