Hi,
I have this scenario:
- browser requests some time-expensive page
- page renders lazy component (instead of regular component) and starts
thread for computation data
- lazy component use Behavior with AJAX callback, timed in seconds
- user sees in browser indicator
- when Behavior fires,
= new Attributes.Name(name);
if (manifest.getMainAttributes().get(attName) != null)
return manifest.getMainAttributes().get(attName).toString();
else
return ;
}
HTH
Martin Schayna
On 12/14/2011 11:45 AM, Sjoerd Schunselaar wrote:
That is the Wicket
yes, some of them :-)
On 02/22/2011 10:04 PM, Jan Ferko wrote:
yes, there are a few.:)
On Tue, 2011-02-22 at 20:32 +0100, Ladislav DANKO wrote:
yes, a lot of ;-)
-Original Message-
From: danisevsky [mailto:danisev...@gmail.com]
Sent: Tuesday, February 22, 2011 4:52 PM
To:
It's problem only {code} segments in wiki pages :)
Workaround: you can see hidden text by editing page -- but you have to
register.
Just click on Edit Page link, than on Preview tab.
Martin Schayna
On 29.4.2010 15:48, Brian Mulholland wrote:
I must be in some minority given
to implement this in my own
RequestCycleProcessor.resolve(), but I hung on searching for page from
requestParameters because Session.getPage() always touches page and it
causes serialization after request processing.
Is there any example, idea, whatever for implementing this in Wicket?
Thanks,
Martin
requestParameters because
Session.getPage() always touches page and it causes serialization after
request processing.
Is there any example, idea, whatever for implementing this in Wicket?
Thanks,
Martin Schayna
?
Hope it's understandable :)
Thank you, Martin Schayna
