I believe the org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(), shold not throw a RunTime Exception as it does now, if the url is tampered, instead it should always provide the parameters and values to it's best guess and then let the user decided how the request needs to be processed.
Also, org.apache.wicket.PageParameters, should provide one iterator with all available params, Any comments? ================================ igor.vaynberg wrote: > > On 8/8/07, Dariusz Wojtas <[EMAIL PROTECTED]> wrote: >> >> I want to use it in cases where the user may be given feeling that he is >> browsing some structure. > > > well, my point was that structure is probably better represented by > indexed > coding strategy, which is forgiving. for example > > /products/clothes/tshirts/red (indexed) > > is better imho then > > /products/category/clothes/subcategory/tshirts/color/red (default) > > -igor > > -- View this message in context: http://www.nabble.com/mountBookmarkablePage-and-missing-parameters---exception-thrown-tf4219655.html#a12590494 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
