hmm i guess it would be easier if we just made this method protected i
think:
AbstractRequestTargetUrlCodingStrategy
private void appendValue(AppendingStringBuffer url, String key, String
value)
and this one is already protected:
protected ValueMap decodeParameters(String urlFragment, Map urlPar
> That takes care of just about everything. However, right about that point,
> you'll likely run into the following bug:
> https://issues.apache.org/jira/browse/WICKET-631.
I hope someone will take a look at that bug sooner or later. The fix is
quite straightforward - moving the finally block
Igor,
I actually did figure out a way to get this working without having to do
any (major) hacking. Pretty simple, too, once I figured it out. I just
created a new IndexedParamResourceUrlCodingStrategy class (included
below) and mounted that. For anyone else looking to do this, here is
the
On 6/30/07, Karl M. Davis <[EMAIL PROTECTED]> wrote:
Hey there all,
I've got a DynamicWebResource that I'm mounting via
mountSharedResource(...) and creating a ResourceLink to. That Resource
requires parameters and I'd love for it to operate similar to how
IndexedParamUrlCodingStrategy works,
Hey there all,
I've got a DynamicWebResource that I'm mounting via
mountSharedResource(...) and creating a ResourceLink to. That Resource
requires parameters and I'd love for it to operate similar to how
IndexedParamUrlCodingStrategy works, where my parameters are numbered
and look like just
