TestParent.java
TestParent.html
TestChild.java
TestChild.html
Output:
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898p4650909.html
Sent from the Users forum mailing list archive
TestChild.html
Output:
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898p4650909.html
Sent from the Users forum mailing list archive at Nabble.com
TestChild.java
TestChild.html
Output:
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898p4650909.html
Sent from the Users forum mailing list archive at Nabble.com
On 01/08/2012 9:58 AM, Martin Grigorov wrote:
No.
The timer is fired but the precondition prevents the Ajax call.
The precondition checks that the component (html element) on which is
attached the timer behavior is still in the DOM document.
Hmm... I don't quite know what to say! In my tests,
Do you use -beta3 ?
There was a bug which is fixed in -SNAPSHOT. That's why I know how it works ;-)
On Wed, Aug 1, 2012 at 5:12 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca wrote:
On 01/08/2012 9:58 AM, Martin Grigorov wrote:
No.
The timer is fired but the precondition prevents the Ajax
Yes I was using -beta3 since this is what Alex used. I just tried it
with -SNAPSHOT (commit b89909c1fa99ae6973c3fb0738a966eb23c27e73) and I
get the same exception.
You say that:
The precondition checks that the component (html element) on which is
attached the timer behavior is still in the
I see.
I'm not sure how Wicket can detect this situation ...
A workaround would require some coding from the developer - when he
replaces the component he has to call additionally:
timerBehavior.stop(target).
This will clear the scheduled timeout in the browser.
On Wed, Aug 1, 2012 at 5:31 PM,
Would this work if done on the client?
New code when ajax response is received :
replacedDOMElement = ...;
$replacedDOMElement = $(replacedDOMElement);
for each js timers:
$component = $(timer.component);
if( $replacedDOMElement.is($component) ||
Yes.
Wicket sends a message on topic '/dom/node/removed' for each removed element.
Using its id we can stop the timer.
Please file the ticket :-)
On Wed, Aug 1, 2012 at 6:20 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca wrote:
Would this work if done on the client?
New code when ajax
Filed WICKET-4689.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
or something else.
My stack trace:
Best regards
Alex
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-tp4650898.html
Sent from the Users forum mailing list archive at Nabble.com
.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-tp4650898.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands
-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898p4650902.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
)
at java.lang.Thread.run(Thread.java:722)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898p4650902.html
Sent from the Users forum mailing list archive at Nabble.com
14 matches
Mail list logo
