On Thu, Mar 7, 2013 at 12:58 PM, Artur wrote:
> On 2013-03-07 11:32, Martin Grigorov wrote:
>
>> Hi,
>>
>> 1) You can add custom IRCLs
>> 2) The IRCL is shared between all sessions so do not keep state in them.
>> You can use RequestCycle's metadata for keeping state
>>
> Thanks for clarification
On 2013-03-07 11:32, Martin Grigorov wrote:
Hi,
1) You can add custom IRCLs
2) The IRCL is shared between all sessions so do not keep state in them.
You can use RequestCycle's metadata for keeping state
Thanks for clarification.
And one more thing.
Is the recommended solution to set MetaData
Hi,
1) You can add custom IRCLs
2) The IRCL is shared between all sessions so do not keep state in them.
You can use RequestCycle's metadata for keeping state
On Thu, Mar 7, 2013 at 12:20 PM, Artur wrote:
> Hi Everybody!
>
> We just migrated from Wicket 1.4 to Wicket 6.6.
> In previous version
Hi Everybody!
We just migrated from Wicket 1.4 to Wicket 6.6.
In previous version we used IRequestCycleProcessor
newRequestCycleProcessor()
Now it is gone and all RequestCycle related methods in Application are
final.
So we thought to add our own listener:
getRequestCycleListeners().add(new C