I am still having exceptions with this. Im using wicket-1.3 snapshots.
(btw, I'm not using wicket's AjaxTabbedPanel, but my own implementations -
altough I don't think that's the problem).
Help is much appreciated
--
View this message in context:
The exception :
java.lang.IndexOutOfBoundsException: Index: 0 at
java.util.Collections$EmptyList.get(Unknown Source) at
org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:88)
at
Should be fixed for 1.3.
-Matej
On 5/11/07, James McLaughlin [EMAIL PROTECTED] wrote:
done!
https://issues.apache.org/jira/browse/WICKET-556
with a brief discussion of other possibilities.
best,
jim
On 5/11/07, Matej Knopp [EMAIL PROTECTED] wrote:
Yeah, looks like a good idea :)
please make a jira issue with the fix you now have
On 5/10/07, Murat Yücel [EMAIL PROTECTED] wrote:
Hi James
Thanks for the fix. It works like a charm :)... Is this something that
wicket will solve
in a future release?
/Murat
2007/5/10, James McLaughlin [EMAIL PROTECTED]:
erm, sorry
Yeah, looks like a good idea :)
On 5/11/07, Johan Compagner [EMAIL PROTECTED] wrote:
please make a jira issue with the fix you now have
On 5/10/07, Murat Yücel [EMAIL PROTECTED] wrote:
Hi James
Thanks for the fix. It works like a charm :)... Is this something that
wicket will solve
done!
https://issues.apache.org/jira/browse/WICKET-556
with a brief discussion of other possibilities.
best,
jim
On 5/11/07, Matej Knopp [EMAIL PROTECTED] wrote:
Yeah, looks like a good idea :)
On 5/11/07, Johan Compagner [EMAIL PROTECTED] wrote:
please make a jira issue with the fix you
Hi All
I had some problem with ajax when using wicket 1.2.6. I read the thread with
the following subject:
Problem with concurren ajax requests on page
Matej suggested that a upgrade to wicket 1.3 would solve the ajax problem.
So i upgraded the application
to wicket-1.3.0-incubating-SNAPSHOT.
Hi Murat,
I posted a hack to fix this several months back:
http://www.nabble.com/AjaxTimer-clearTimeout-tf3364438.html#a9360559
Essentially, I have the timer check if the markup for the component it was
bound to is still in the page, and return without firing if it is not. Hope
this helps.
erm, sorry that was:
http://www.nabble.com/Re%3A-AjaxTimer-clearTimeout-p9401965.html
On 5/10/07, James McLaughlin [EMAIL PROTECTED] wrote:
Hi Murat,
I posted a hack to fix this several months back:
http://www.nabble.com/AjaxTimer-clearTimeout-tf3364438.html#a9360559
Essentially, I have the
Hi James
Thanks for the fix. It works like a charm :)... Is this something that
wicket will solve
in a future release?
/Murat
2007/5/10, James McLaughlin [EMAIL PROTECTED]:
erm, sorry that was:
http://www.nabble.com/Re%3A-AjaxTimer-clearTimeout-p9401965.html
On 5/10/07, James McLaughlin
10 matches
Mail list logo
