Maybe use an IRequestCycleListener and maybe use
On Sun, Jan 5, 2014 at 4:15 AM, jchappelle wrote:
> We get a lot of ComponentNotFoundExceptions in production and I have not
> been
> able to reproduce them. I've had discussions on here before about this and
> I
> think what is happening is th
Maybe use an IRequestCycleListener and maybe use onRequestHandlerExecuted.
See
private void execute(IRequestHandler handler)
{
Args.notNull(handler, "handler");
try
{
listeners.onRequestHandlerResolved(this, handler);
requestHandlerExecutor.execute(handler);
listeners.onRequestHandlerExecuted(thi
Hi Josh,
We also had that "ComponentNotFoundException" problem so now and
then.
My experience might be a different than yours but I'll mention it anyway,
you never know!.
From my experience with our clients, when the client has to wait a bit
longer, he/she re-clicks the same ajax link, where tha
I've solved this problem before but can't remember how I did it. The
wicket-el example app is running on google app engine which unloads the
instance if it's not accessed for a period of time. This is ok if the
next user hits the "/" url first but if they try to hit any mounted urls
e.g. /ajax th
Thanks for the replies.
Marco there is a good possibility that is what we are facing too. I have
just been guessing at the causes at this point and haven't considered the
double click.
I wonder if there is there a more global way to set that for all Ajax links
instead of creating a custom AjaxLin
I have found the issue and I can finally reproduce it!
The issue is similar to what you described. We have a dashboard panel that
has several tabs. Those tabs are ajax tabs. If a user clicks a tab and it
takes a while to load then they click on a link on the current tab while
waiting then you will
That's great!
For tabbed panels that take a while to load I just apply lazy loading panels,
that way that tab gets "loaded" immediately and an indicator is shown that the
panel is being loaded.
The user knows that the panel is being loaded and is unable to click any links
on the "old" panel.
I
That's a good point. We use those in a lot of our data tables that take a
while to load. In fact I have created a base class that hides that and
automatically wraps the DataTable in an AjaxLazyLoadPanel. I might make a
custom TabbedPanel that wraps the panel in an AjaxLazyLoadPanel.
--
View this
Another way to achieve this is using a blocking layer...
On Sun, Jan 5, 2014 at 6:05 PM, jchappelle wrote:
> Thanks for the replies.
>
> Marco there is a good possibility that is what we are facing too. I have
> just been guessing at the causes at this point and haven't considered the
> double
That's what I use as well, depending on the scenario.
Usually when there's a second modal window open, and closing that second modal
requiring the first modal window to do a repaint on it's current content, I
display a blocking layer, if the process takes longer than average (e.g. >~8
seconds).
Can't you simply invalidate the user session and have Wicket redirect to / when
that happens?
Another idea, have an Ajax timer refresh those resources so they don't time out
:)
Have a great day,
Paul Bors
> On Jan 5, 2014, at 7:55 AM, Steve wrote:
>
> I've solved this problem before but
There are some global callbacks [1]. You might be able to use
Global Ajax call listeners
IAjaxCallListener's can be used to listen for the lifecycle of an Ajax call
for a specific component.
If the user application needs to listen for all Ajax calls then it may
subscribe to the following topics:
oops... Seems I had a little brain fade. I was mounting the urls in the
onInitialize method of the common page superclass so they aren't mounted
until you hit the home page which is the only page accessible at that
point. Not a good design idea ;)
On 06/01/14 08:09, Paul Borș wrote:
> Can't you si
I have exactly the same problem.
I have tracked the cause:
All AJAX behaviors are bounded to the first element, because all child
elements in a ListView have the same generated HTML ids.
Actually when you trigger an event on first element in ListView the number
of AJAX requests that were sent is e
I think I don't understood.
I try to create an other FormTester to perform the submit() like that:
FooPage page = this.tester.startPage(FooPage.class);
FormTester formTester = this.tester.newFormTester("form");
formTester.setValue("textField", "FOO");
formTester.select("dropDownChoice", 0); // ony
15 matches
Mail list logo
