you can provide your own subclass of webresponse and override
encodeurl the same way. see WebApplication#newWebResponse
-igor
On Mon, May 4, 2009 at 2:25 PM, Matt Welch <matt...@welchkin.net> wrote:
>
> I'm not worried about the multiple window thing. FWIW I believe that value is
> set to true by default anyway. I'm just wondering if there's a way to add a
> parameter to each link on page to ensure that the next page stays in the
> same context.
>
> For instance, when I was trying to solve an unrelated problem, the servlet
> filter I was working with tied itself directly into the response.encodeUrl()
> method so that each call to that method would also use the filter's specific
> instructions as well.
>
> I was hoping that there might be something similar for links in Wicket where
> every link, no matter how it's generated (except manually in HTML, of
> course) would be handled by a particular method that I could put a hook into
> to make sure my context specific request parameter got added.
>
> -Matt
>
>
>
>
>
> Martin Funk-3 wrote:
>>
>> maybe automatic multi window support might help you
>>
>> this can be turned on like this in the init method of your Application.
>>
>> /**
>> * @see org.apache.wicket.protocol.http.WebApplication#init()
>> */
>> @Override
>> protected void init()
>> {
>> super.init();
>> getPageSettings().setAutomaticMultiWindowSupport(true);
>> }
>>
>> mf
>>
>> Am 03.05.2009 um 15:00 schrieb Matthew Welch:
>>
>>> The data in the application that I'm working on is divided in any
>>> number of
>>> different contexts. The pages displayed for each context are the
>>> same but
>>> the data shown on those pages will be different depending on the
>>> specific
>>> context. A logged in user might might have multiple pages (browser
>>> windows)
>>> open at one time from any one of these contexts, otherwise I would
>>> store the
>>> context in their session. As it stands I need to pass the context
>>> around
>>> from page to page as a parameter. Is there an easy way to have this
>>> parameter automatically appended to all links on page as they are
>>> rendered
>>> or generated?
>>>
>>> I suppose I could build my own set of Link components that look for
>>> the
>>> existing context of a page and append that to themselves, and use
>>> those
>>> links instead of the built in ones. Any other options?
>>>
>>> -Matt
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Automatically-adding-a-parameter-to-every-link--tp23355558p23376936.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
