) );
}
When I use the url:
https://lilo:8443/whisky/app/cat/?id=1
Not to mention that i have been using the Nice Url here for the above class.
I get the following in consol output:
Param = null
Can anyone point out what may b wrong? I expected it to be:
Param = 1
--
View this message in context:
http
.
I get the following in consol output:
Param = null
Can anyone point out what may b wrong? I expected it to be:
Param = 1
--
View this message in context:
http://www.nabble.com/Param-%3D-null-tf4413478.html#a12589727
Sent from the Wicket - User mailing list archive at Nabble.com
Simply Amazing! It works like a charm.
So the Wicket syntx is:
https://lilo:8443/whisky/app/cat/param1/value1/param2/value2
Gracias para la ayuda Fancis!
=
tried https://lilo:8443/whisky/app/cat/id/1 ?
--
View this message in context:
that is the default, you can changed it using a different UrlCodingStrategy
On 9/10/07, chickabee [EMAIL PROTECTED] wrote:
Simply Amazing! It works like a charm.
So the Wicket syntx is:
https://lilo:8443/whisky/app/cat/param1/value1/param2/value2
Gracias para la ayuda Fancis!
Thanks again, and what will be the best way to make these url temper proof?
Currently, if i break the key value pairs, the wicket app is very unhappy
like below:
Unexpected RuntimeException
Root cause:
java.lang.IllegalStateException: URL fragment has unmatched key/value pair:
name/foo/id
at
no it is not! - its just 1 way the wicket syntax may be - you should
look at mount and the existing coding-strategys as well as (if youre on
1.3 already) on the new HybridUrlCodingStrategy
you can have fllowing URL flavors out of box:
/app/page/value1/value2
(IndexedURLCoding)
/app/page:0
On 9/10/07, chickabee [EMAIL PROTECTED] wrote:
These strategies are pretty nice, but the question remains why the
decoder()
method pukes out when there is mismatch of key value pairs. Hacker will be
very happy with the current state of implementation.
only if you deploy your application in
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
only if you deploy your application in development mode. in deployment mode
only the internal error page.
see IApplicationSettings#setInternalErrorPage(Class)
gerolf
Thanks for the good piece of info.
I still do not see why the wicket should treat it as an internal error if
there are missing
Yes you are right.
I guess the the name u were looking for is:
org.apache.wicket.request.target.coding.MixedParamUrlCodingStrategy
These strategies are pretty nice, but the question remains why the decoder()
method pukes out when there is mismatch of key value pairs. Hacker will be
very happy
I would disagree because this is the first problem any web developer would
like to address, what happens if their urls are being tempered manually, it
should not result into any kind of error by the web framework, rather this
is the application validation issue and to be handled by the
Pardon? All that's doing is showing their custom error page, exactly
as the other replies have suggested that you'd want to do with Wicket
- I'd be more impressed if it had shown an index of the news for that
date, but as it is, that's just what you can easily do with Wicket.
All you need to do
Ok, let me give you a different scenario and see if wicket has a way to
handle it.
Assume there are 10 parameters are being passed to the app as below:
http://some.web.site/wicket/app/page/p1/v1/p2/v2/p3/v3/...p9/v9/p10/v10
Now If I mess-up the key value pair at the end like:
You write your own coding strategy, using the existing ones as
guidelines/templates - I've not got any example code as supporting
free-format user-created URL's isn't a scenario that's been relevant
in the applications I've done.
Wicket provides a number of strategies, but the fundamental point
Thanks Gwyn for all the clarifications and patience, I believe I have all the
answers now.
Also, what's your take on adding an iterator to PageParameters that will
help in looping over the parameters, rather than pulling them one at at time
the way it is right now. I'm not sure if the same can
15 matches
Mail list logo
