As you're already overriding decodeParamaters(), what about a cut &
paste of the code from there & appendParameters(), changing it to use
some other character (that you won't have in your params), e.g. '|' or
'^', leaving the '/' to become a non-special char?

/Gwyn


On 07 November 2007, 10:09:57 PM, green804 wrote:
g> We are using 1.2.6 right now.  The Food%2FDrink is one param.  That param
g> does have a /.  Unfortunately, I can't change the param.  I'm overriding the
g> decodeParameters to handle the case with mismatched key/value pairs, but
g> it's kind of a hack because I have to know which params might have a /.
g> It's not a very generic solution.  I'm hoping to track down where the decode
g> is happening in the first place and override that instead.  



g> Johan Compagner wrote:
>> 
>> what are you doing then in your own
>> BookmarkablePageRequestTargetUrlCodingStrategy?
>> 
>> who generates that url? and what is that Food%2FDrink? Should that be 1
>> param? And has the param a /?
>> 
>> which version do you use?
>> 
>> 
>> On 11/7/07, green804 <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>> I am having a problem with the UrlCodingStrategy.  I'm currently
>>> extending
>>> BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the
>>> app
>>> is decoding some of the characters in the url before I get the url in the
>>> decodeParameters method.
>>>
>>> For example, the url once encoded looks like this:
>>>
>>> /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink
>>>
>>> where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink
>>>
>>> When the decode method in BookmarkablePageRequestTargetUrlCodingStrategy
>>> calls requestParameters.getPath() the url looks like this:
>>>
>>> /linkframe/item/187822/site/Wine/sitetopic/Food/Drink
>>>
>>> This is causing a problem because the app thinks the URL fragment has
>>> unmatched key/value pairs.  I cannot seem to find where/why the %2F is
>>> getting resolved to a /.  Can someone help me with this?  I need to keep
>>> this from happening.  It's causing null pointers all over the place.
>>> --
>>> View this message in context:
>>> http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974
>>> Sent from the Wicket - User mailing list archive at Nabble.com.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to