On Monday, September 10, 2007, 12:23:36 PM, chickabee <[EMAIL PROTECTED]> wrote:
> I still do not see why the wicket should treat it as an internal error if > there are missing parameters? I guess wicket needs to follow the same > paradigm as in the raw HttpRequest, let the user pull the parameters if they > exist and take their own decision if they do not. It does not make any sense > for the Wicket to declare the state of emergency if the parameters key > value do not match. Normally, it does, as in most cases the link would have been generated by the web-app or another external web-app, so if it's missing/corrupt, something odd is going on. You, of course, have the option to supply your own strategy if you want to attempt to cater for users doing partial/incorrect edits of the URL, and having your strategy guess what they meant, but it's rather an isolated requirement, so I don't think it would belong in the core... If you're trying to /avoid/ users editing the URL, however, there are other coding strategies for that that encrypt & decrypt the URLs... /Gwyn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
