Iframe problem with jQuery 1.10.1 in IE
Hi, if iframe content (Wicket page) is loaded from external domain loading of jQuery 1.10.1 (and Wicket) fails due to a bug http://bugs.jquery.com/ticket/13980 This has been fixed in jQuery 1.10.2 that we are now using by setting JQueryReference and it seems to work fine, -Heikki
RE: Re:aj Component twice in markup while ax refresh in Wicket 6.7 (migrated from 1.5.10)
Hi,
we had similar issue and could not find jira ticket for this, thus created
WICKET-5210 with quickstart.
Our workaround was changing our jQuery('#someid').. to jQuery('[id=someid]')..
to match all same (two) ids.
Rgds,
Heikki
-Original Message-
From: Nico [mailto:nico.kan...@gmx.de]
Sent: 15. toukokuuta 2013 11:07
To: users@wicket.apache.org
Subject: Re:aj Component twice in markup while ax refresh in Wicket 6.7
(migrated from 1.5.10)
Hi,
thanks for you quick replies! I will create the quick start and attach it to a
jira ticket.
Thanks to your hint Martin, for the moment I will use jQuery#replaceWith() to
make sure my app runs as expected.
Best
Nico
Am 14.05.2013 um 16:56 schrieb Martin Grigorov-4 [via Apache Wicket]:
Hi,
We use
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java
/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js#L1617
because
it is faster than jQuery#replaceWith().
So yes, there is a small period when both the old and the new are in
the DOM.
As Sven asked - please create a quicktart and attach it to a ticket so
we can see whether we will find a solution or we will have to use the
slower way to replace.
On Tue, May 14, 2013 at 4:48 PM, Sven Meier [hidden email] wrote:
Create a quickstart and attach it to a Jira issue please.
Sven
On 05/14/2013 04:37 PM, Nico wrote:
Hi
I migrated my application from Wicket 1.5.10 to 6.7
During testing I recognized that during an ajax update
(replacement) of a component, the markup of the component is twice
in the HTML markup (the old and the new markup). Thus the execution
of javascript inside a component may fail due to the fact, that two
components with the same id are present in the HTML markup.
EXAMPLE
*HTML:*
lt;a wicket:id=quot;testlinkquot;**gt;testlinklt;/agt;
lt;div wicket:id=quot;testboxquot; style=quot;width: 100px; height:
100px; border: 1px solid #ccc;quot;gt;
lt;script type=quot;text/javascript**quot;gt;
alert(#39;hello#39;);
lt;/scriptgt;
lt;/divgt;
*JAVA:*
final WebMarkupContainer testbox = new
WebMarkupContainer(testbox); testbox.setOutputMarkupId(**true);
add(testbox);
add(new AjaxLinkVoid(testlink) {
private static final long serialVersionUID = 1L;
@Override
public void onClick(AjaxRequestTarget target) {
target.add(testbox);
}
});
So while the ajax update is processed the 'testbox' DIV and its
javascript are present twice (the old and new DIV). If the
javascript is a little more complex and for example changes stuff
inside the DIV, the javascript will change stuff in the old instead
of the new DIV container.
My javascript relies on the fact, that an id should always be
present just once.
Why is the old DIV not removed first, before the new DIV is
appended? Can I change this behavior somehow?
Thanks in advance
Nico
--
View this message in context: http://apache-wicket.1842946.**
n4.nabble.com/Component-twice-**in-markup-while-ajax-refresh-**
in-Wicket-6-7-migrated-from-1-**5-10-tp4658789.htmlhttp://apache-w
icket.1842946.n4.nabble.com/Component-twice-in-markup-while-ajax-re
fresh-in-Wicket-6-7-migrated-from-1-5-10-tp4658789.html
Sent from the Users forum mailing list archive at Nabble.com.
--**--**---
-- To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.org[hidden email] For
additional commands, e-mail: [hidden email]
--**--**
- To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.org[hidden email] For additional
commands, e-mail: [hidden email]
--
Martin Grigorov
Wicket Training Consulting
http://jWeekend.com http://jweekend.com/
If you reply to this email, your message will be added to the discussion
below:
http://apache-wicket.1842946.n4.nabble.com/Component-twice-in-markup-w
hile-ajax-refresh-in-Wicket-6-7-migrated-from-1-5-10-tp4658789p4658791
.html To unsubscribe from Component twice in markup while ajax refresh
in Wicket 6.7 (migrated from 1.5.10), click here.
NAML
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Component-twice-in-markup-while-ajax-refresh-in-Wicket-6-7-migrated-from-1-5-10-tp4658789p4658813.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
As expected KB2675157 fixed this IE9 issue, nice timing though. -Original Message- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 12. huhtikuuta 2012 10:18 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Ok, it seems that time takes care of this problem and leak is not wicket-ajax problem: Tests with IE 10 (consumer preview) shows no leaking, gc seems to work and browser refresh clears the memory. There were no leaking with Opera, Firefox and Chrome. Furthermore previous JS debugging did not show that anything was piling in dom, so it must be IE9 inner problem. Only leaking is this IE9 in IE9 document mode, can't see any point filing a ticket. Anyway quickstart is available at http://uploading.com/files/51fc2bcb/ie9memory.zip/ Easy way to check Process Explorer - select iexplore.exe- Properties..- Performance Graph - Private bytes -Original Message- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 11. huhtikuuta 2012 14:38 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, 1) Process Explorer and IE developer tools 2) ok -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 11. huhtikuuta 2012 14:14 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, From your mails I still don't understand how exactly you measure the memory consumption. You have two options: 1) google for javascript memory leak. You can add Internet explorer in the search term too I'm not sure whether IE has tools to deal with that but you can use and see whether it helps somehow 2) create a ticket in Wicket Jira with a quickstart and detailed description how to reproduce and how to measure and let someone else to debug it for you. On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen heikki.uoti...@syncrontech.com wrote: Hi, I tested against apache-wicket-6.0.0-beta1 with that simple example in the first mail. Application still leaked memory on IE9 document mode, same behavior as with 1.5.5. Confirmed that it is using jQuery: script type=text/javascript src=../resource/org.apache.wicket.resource.JQueryResourceReference/jq uery/jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-event-jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-ajax-jquery-ver-1334139767559.js/script Suggestions ? -Original Message- From: Chris Colman [mailto:chr...@stepaheadsoftware.com] Sent: 11. huhtikuuta 2012 11:47 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) how exactly did you solve it with jQuery ? Since this leak seems to be caused by wicket-ajax calls then solution would be bypassing those, this would be the last resort. Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your app were ported to Wicket 6 if the IE9 problem goes away. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Ok, it seems that time takes care of this problem and leak is not wicket-ajax problem: Tests with IE 10 (consumer preview) shows no leaking, gc seems to work and browser refresh clears the memory. There were no leaking with Opera, Firefox and Chrome. Furthermore previous JS debugging did not show that anything was piling in dom, so it must be IE9 inner problem. Only leaking is this IE9 in IE9 document mode, can't see any point filing a ticket. Anyway quickstart is available at http://uploading.com/files/51fc2bcb/ie9memory.zip/ Easy way to check Process Explorer - select iexplore.exe- Properties..- Performance Graph - Private bytes -Original Message- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 11. huhtikuuta 2012 14:38 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, 1) Process Explorer and IE developer tools 2) ok -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 11. huhtikuuta 2012 14:14 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, From your mails I still don't understand how exactly you measure the memory consumption. You have two options: 1) google for javascript memory leak. You can add Internet explorer in the search term too I'm not sure whether IE has tools to deal with that but you can use and see whether it helps somehow 2) create a ticket in Wicket Jira with a quickstart and detailed description how to reproduce and how to measure and let someone else to debug it for you. On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen heikki.uoti...@syncrontech.com wrote: Hi, I tested against apache-wicket-6.0.0-beta1 with that simple example in the first mail. Application still leaked memory on IE9 document mode, same behavior as with 1.5.5. Confirmed that it is using jQuery: script type=text/javascript src=../resource/org.apache.wicket.resource.JQueryResourceReference/jq uery/jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-event-jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-ajax-jquery-ver-1334139767559.js/script Suggestions ? -Original Message- From: Chris Colman [mailto:chr...@stepaheadsoftware.com] Sent: 11. huhtikuuta 2012 11:47 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) how exactly did you solve it with jQuery ? Since this leak seems to be caused by wicket-ajax calls then solution would be bypassing those, this would be the last resort. Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your app were ported to Wicket 6 if the IE9 problem goes away. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
it seems that IE9 leaks memory heavily when updating components with Ajax in
IE9 document mode.
can anyone confirm if this is Wicket related issue ?
Forcing IE8 document mode will cause some problems in the future.
Our use case is process displays where data comes from automation or other
systems and data
is updated frequently and those monitoring displays are open 24/7. Large
customers have their
own standards for browsers and versions they are using.
If there are 50 simple text divs on the screen, then updating those every 10
seconds
browser window consumes memory 3Mb in a minute in IE9 document mode, refreshing
browser
does not release memory. Normally updates happens more irregular and updating
all fields
at once makes user experience less comfortable 'cause there are other actions
connected
to those fields (links, tooltips, graphics).
how exactly did you solve it with jQuery ?
Since this leak seems to be caused by wicket-ajax calls then solution would be
bypassing
those, this would be the last resort.
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 5. huhtikuuta 2012 18:50
To: users@wicket.apache.org
Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
maybe there is some gc problem with closures in IE9 document mode.
Simple test page leaks memory in IE9 mode even if first suspect
Wicket.replaceOuterHtmlIE is commented out. Test with plain XMLHttpRequest does
not leak memory in any case.
This Wicket Ajax example also slowly grows if IE9 document mode is set manually
but is not seemingly leaking in IE8 mode
http://www.wicket-library.com/wicket-examples/ajax/world-clock
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: 4. huhtikuuta 2012 9:19
To: users@wicket.apache.org
Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
Can you share your findings ?
What exactly you think caused the memory leak and how exactly did you solve it
with jQuery ?
On Wed, Apr 4, 2012 at 8:14 AM, Heikki Uotinen heikki.uoti...@syncrontech.com
wrote:
Ok, this leak can be avoided by updating rapidly changing components
with jQuery before upgrading to Wicket 6,
-Heikki
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 3. huhtikuuta 2012 16:17
To: users@wicket.apache.org
Subject: IE9 Memory leak when updating component with Ajax (Wicket
1.5.5)
Hi,
it seems that IE9 leaks memory heavily when updating components with Ajax in
IE9 document mode.
There is no leak after setting document to IE8 mode
meta http-equiv=X-UA-Compatible content=IE=8/
Any ideas to resolve this without forcing IE8 mode ?
There have been past issues, but found no current issue related to this,
quick start code is very simple, Opera, Firefox, Chrome work fine.
public HomePage(final PageParameters parameters)
{
Label testDiv = new Label(testDiv, new
PropertyModel(this, data));
testDiv.setOutputMarkupId(true);
add(testDiv);
AjaxSelfUpdatingTimerBehavior timer = new
AjaxSelfUpdatingTimerBehavior(Duration.milliseconds(200));
testDiv.add(timer);
}
public String getData()
{
Date now = new Date();
return now.toString();
}
html
head
!-- No leak if this is set
meta http-equiv=X-UA-Compatible
content=IE=8/
--
/head
body
div wicket:id=testDiv/div
/body
/html
-Heikki
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
B CB [
X ܚX KK[XZ[
\ \ ][ X ܚX P X ]
\X K ܙ B ܈Y][ۘ[ [X[ K[XZ[
\ \ Z[ X ]
\X K ܙ B
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi, I tested against apache-wicket-6.0.0-beta1 with that simple example in the first mail. Application still leaked memory on IE9 document mode, same behavior as with 1.5.5. Confirmed that it is using jQuery: script type=text/javascript src=../resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-event-jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1334139767559.js/script Suggestions ? -Original Message- From: Chris Colman [mailto:chr...@stepaheadsoftware.com] Sent: 11. huhtikuuta 2012 11:47 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) how exactly did you solve it with jQuery ? Since this leak seems to be caused by wicket-ajax calls then solution would be bypassing those, this would be the last resort. Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your app were ported to Wicket 6 if the IE9 problem goes away. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi, 1) Process Explorer and IE developer tools 2) ok -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 11. huhtikuuta 2012 14:14 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, From your mails I still don't understand how exactly you measure the memory consumption. You have two options: 1) google for javascript memory leak. You can add Internet explorer in the search term too I'm not sure whether IE has tools to deal with that but you can use and see whether it helps somehow 2) create a ticket in Wicket Jira with a quickstart and detailed description how to reproduce and how to measure and let someone else to debug it for you. On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen heikki.uoti...@syncrontech.com wrote: Hi, I tested against apache-wicket-6.0.0-beta1 with that simple example in the first mail. Application still leaked memory on IE9 document mode, same behavior as with 1.5.5. Confirmed that it is using jQuery: script type=text/javascript src=../resource/org.apache.wicket.resource.JQueryResourceReference/jq uery/jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-event-jquery-ver-1334139767559.js/script script type=text/javascript src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re s/js/wicket-ajax-jquery-ver-1334139767559.js/script Suggestions ? -Original Message- From: Chris Colman [mailto:chr...@stepaheadsoftware.com] Sent: 11. huhtikuuta 2012 11:47 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) how exactly did you solve it with jQuery ? Since this leak seems to be caused by wicket-ajax calls then solution would be bypassing those, this would be the last resort. Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your app were ported to Wicket 6 if the IE9 problem goes away. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
maybe there is some gc problem with closures in IE9 document mode.
Simple test page leaks memory in IE9 mode even if first suspect
Wicket.replaceOuterHtmlIE
is commented out. Test with plain XMLHttpRequest does not leak memory in any
case.
This Wicket Ajax example also slowly grows if IE9 document mode is set manually
but is not
seemingly leaking in IE8 mode
http://www.wicket-library.com/wicket-examples/ajax/world-clock
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: 4. huhtikuuta 2012 9:19
To: users@wicket.apache.org
Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
Can you share your findings ?
What exactly you think caused the memory leak and how exactly did you solve it
with jQuery ?
On Wed, Apr 4, 2012 at 8:14 AM, Heikki Uotinen heikki.uoti...@syncrontech.com
wrote:
Ok, this leak can be avoided by updating rapidly changing components
with jQuery before upgrading to Wicket 6,
-Heikki
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 3. huhtikuuta 2012 16:17
To: users@wicket.apache.org
Subject: IE9 Memory leak when updating component with Ajax (Wicket
1.5.5)
Hi,
it seems that IE9 leaks memory heavily when updating components with Ajax in
IE9 document mode.
There is no leak after setting document to IE8 mode
meta http-equiv=X-UA-Compatible content=IE=8/
Any ideas to resolve this without forcing IE8 mode ?
There have been past issues, but found no current issue related to this,
quick start code is very simple, Opera, Firefox, Chrome work fine.
public HomePage(final PageParameters parameters)
{
Label testDiv = new Label(testDiv, new
PropertyModel(this, data));
testDiv.setOutputMarkupId(true);
add(testDiv);
AjaxSelfUpdatingTimerBehavior timer = new
AjaxSelfUpdatingTimerBehavior(Duration.milliseconds(200));
testDiv.add(timer);
}
public String getData()
{
Date now = new Date();
return now.toString();
}
html
head
!-- No leak if this is set
meta http-equiv=X-UA-Compatible
content=IE=8/
--
/head
body
div wicket:id=testDiv/div
/body
/html
-Heikki
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Ok, this leak can be avoided by updating rapidly changing components with
jQuery
before upgrading to Wicket 6,
-Heikki
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 3. huhtikuuta 2012 16:17
To: users@wicket.apache.org
Subject: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
it seems that IE9 leaks memory heavily when updating components with Ajax in
IE9 document mode.
There is no leak after setting document to IE8 mode
meta http-equiv=X-UA-Compatible content=IE=8/
Any ideas to resolve this without forcing IE8 mode ?
There have been past issues, but found no current issue related to this, quick
start code is very simple, Opera, Firefox, Chrome work fine.
public HomePage(final PageParameters parameters)
{
Label testDiv = new Label(testDiv, new
PropertyModel(this, data));
testDiv.setOutputMarkupId(true);
add(testDiv);
AjaxSelfUpdatingTimerBehavior timer = new
AjaxSelfUpdatingTimerBehavior(Duration.milliseconds(200));
testDiv.add(timer);
}
public String getData()
{
Date now = new Date();
return now.toString();
}
html
head
!-- No leak if this is set
meta http-equiv=X-UA-Compatible content=IE=8/
--
/head
body
div wicket:id=testDiv/div
/body
/html
-Heikki
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi,
it seems that IE9 leaks memory heavily when updating components with Ajax in
IE9 document mode.
There is no leak after setting document to IE8 mode
meta http-equiv=X-UA-Compatible content=IE=8/
Any ideas to resolve this without forcing IE8 mode ?
There have been past issues, but found no current issue related to this, quick
start code is very simple,
Opera, Firefox, Chrome work fine.
public HomePage(final PageParameters parameters)
{
Label testDiv = new Label(testDiv, new
PropertyModel(this, data));
testDiv.setOutputMarkupId(true);
add(testDiv);
AjaxSelfUpdatingTimerBehavior timer = new
AjaxSelfUpdatingTimerBehavior(Duration.milliseconds(200));
testDiv.add(timer);
}
public String getData()
{
Date now = new Date();
return now.toString();
}
html
head
!-- No leak if this is set
meta http-equiv=X-UA-Compatible content=IE=8/
--
/head
body
div wicket:id=testDiv/div
/body
/html
-Heikki
RE: Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax
Thanks,
https://issues.apache.org/jira/browse/WICKET-2457
-Heikki
-Original Message-
From: Matej Knopp [mailto:matej.kn...@gmail.com]
Sent: 9. syyskuuta 2009 0:10
To: users@wicket.apache.org
Subject: Re: Flash/ExternalInterface does not work in IE if movie is fetched
via Wicket/Ajax
Hi,
can you create jira issue with problem description? The code indeed
looks wrong I can fix it once the issue is created.
-Matej
On Tue, Sep 8, 2009 at 9:59 PM, Heikki
Uotinenheikki.uoti...@syncrontech.com wrote:
There is a bug in wicket-ajax.js:268 (1.4.1) that breaks
IE+Flash/ExternalInterface:
// place all newly created elements before the old element
while(tempParent.childNodes.length 0) {
var tempElement = tempParent.childNodes[0];
tempParent.removeChild(tempElement);
parent.insertBefore(tempElement, element);
tempElement = null;
}
Calling removeChild is not needed because insertBefore moves element from its
original place.
If you remove removeChild line and check tempParent.childNodes.length you
can see that it is
decreased by one after insertBefore.
This removeChild breaks Flash/ExternalInterface in IE. If removeChild is
removed then everything
works fine. IE is more strict here than other browsers.
Demonstration is still at (there is no need for Flash CS4 to test this)
http://download.syncrontech.com/public/quickstart_noname.zip
Could someone confirm this and suggest how to proceed ?
-Heikki
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 7. syyskuuta 2009 9:21
To: users@wicket.apache.org
Subject: RE: Flash/ExternalInterface does not work in IE if movie is fetched
via Wicket/Ajax
There is a problem with IE/ExternalInterface if movie is added to DOM f.ex
appendChild
JavaScript functions are called but they do not return any value.
This is clearly MS problem but could IE specific function in wicket-ajax.js
be adjusted somehow ?
Simple test case has
var flashMovie = 'OBJECT id=testId codeBase=http://fpdownload..
// Works in IE and FF
document.getElementById(testdiv).innerHTML = flashMovie;
// ExternalInterface.call calls JS but does not return value in IE.
Works in FF
var tempDiv = document.createElement(div);
tempDiv.innerHTML = flashMovie;
document.body.appendChild(tempDiv);
Here is complete code (ajax.swf can be found in zip files)
http://pastebin.com/fbc0aa9a
Here is AS3 code in ajax.fla
http://pastebin.com/d4efd47b
-Heikki
-Original Message-
From: Mikko Pukki [mailto:mikko.pu...@syncrontech.com]
Sent: 4. syyskuuta 2009 15:33
To: users@wicket.apache.org
Subject: Flash/ExternalInterface does not work in IE if movie is fetched via
Wicket/Ajax
Hi,
This example demonstrates that ExternalInterface fails with IE only if movie
is fetched via Wicket/Ajax.
ajaxtest.zip:
(http://download.syncrontech.com/public/ajaxtest.zip)
Page first.html fetches second.html page via Ajax. Second.html has Flash
movie
that calls JavaScript methods with ExternalInterface and produces output
Start...
ExternalInterface.available:true
ExternalInterface.objectID:testId
fromJs:text from js (first.html)
This works both FF 3.5 and IE 7/IE8
quickstart_noname.zip:
(http://download.syncrontech.com/public/quickstart_noname.zip)
Same demonstration with wicket. This fails with IE
Start...
ExternalInterface.available:true
ExternalInterface.objectID:null
fromJs:null
ObjectId is null and JavaScript call does not return any value.
We are aware about EI/IE problems in past, but any of those does not seem to
fit here.
Wicket 1.4.1, Flash Player 10, IE 7/8, FF 3.5
Has anyone encountered any similar behavior and/or has found any workaround?
Should I create a Jira issue?
--
Mikko Pukki
Syncron Tech Oy
Laserkatu 6
53850 Lappeenranta
+358 400 757 178
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax
There is a bug in wicket-ajax.js:268 (1.4.1) that breaks
IE+Flash/ExternalInterface:
// place all newly created elements before the old element
while(tempParent.childNodes.length 0) {
var tempElement = tempParent.childNodes[0];
tempParent.removeChild(tempElement);
parent.insertBefore(tempElement, element);
tempElement = null;
}
Calling removeChild is not needed because insertBefore moves element from its
original place.
If you remove removeChild line and check tempParent.childNodes.length you
can see that it is
decreased by one after insertBefore.
This removeChild breaks Flash/ExternalInterface in IE. If removeChild is
removed then everything
works fine. IE is more strict here than other browsers.
Demonstration is still at (there is no need for Flash CS4 to test this)
http://download.syncrontech.com/public/quickstart_noname.zip
Could someone confirm this and suggest how to proceed ?
-Heikki
-Original Message-
From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com]
Sent: 7. syyskuuta 2009 9:21
To: users@wicket.apache.org
Subject: RE: Flash/ExternalInterface does not work in IE if movie is fetched
via Wicket/Ajax
There is a problem with IE/ExternalInterface if movie is added to DOM f.ex
appendChild
JavaScript functions are called but they do not return any value.
This is clearly MS problem but could IE specific function in wicket-ajax.js be
adjusted somehow ?
Simple test case has
var flashMovie = 'OBJECT id=testId codeBase=http://fpdownload..
// Works in IE and FF
document.getElementById(testdiv).innerHTML = flashMovie;
// ExternalInterface.call calls JS but does not return value in IE.
Works in FF
var tempDiv = document.createElement(div);
tempDiv.innerHTML = flashMovie;
document.body.appendChild(tempDiv);
Here is complete code (ajax.swf can be found in zip files)
http://pastebin.com/fbc0aa9a
Here is AS3 code in ajax.fla
http://pastebin.com/d4efd47b
-Heikki
-Original Message-
From: Mikko Pukki [mailto:mikko.pu...@syncrontech.com]
Sent: 4. syyskuuta 2009 15:33
To: users@wicket.apache.org
Subject: Flash/ExternalInterface does not work in IE if movie is fetched via
Wicket/Ajax
Hi,
This example demonstrates that ExternalInterface fails with IE only if movie is
fetched via Wicket/Ajax.
ajaxtest.zip:
(http://download.syncrontech.com/public/ajaxtest.zip)
Page first.html fetches second.html page via Ajax. Second.html has Flash
movie
that calls JavaScript methods with ExternalInterface and produces output
Start...
ExternalInterface.available:true
ExternalInterface.objectID:testId
fromJs:text from js (first.html)
This works both FF 3.5 and IE 7/IE8
quickstart_noname.zip:
(http://download.syncrontech.com/public/quickstart_noname.zip)
Same demonstration with wicket. This fails with IE
Start...
ExternalInterface.available:true
ExternalInterface.objectID:null
fromJs:null
ObjectId is null and JavaScript call does not return any value.
We are aware about EI/IE problems in past, but any of those does not seem to
fit here.
Wicket 1.4.1, Flash Player 10, IE 7/8, FF 3.5
Has anyone encountered any similar behavior and/or has found any workaround?
Should I create a Jira issue?
--
Mikko Pukki
Syncron Tech Oy
Laserkatu 6
53850 Lappeenranta
+358 400 757 178
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax
There is a problem with IE/ExternalInterface if movie is added to DOM f.ex appendChild JavaScript functions are called but they do not return any value. This is clearly MS problem but could IE specific function in wicket-ajax.js be adjusted somehow ? Simple test case has var flashMovie = 'OBJECT id=testId codeBase=http://fpdownload.. // Works in IE and FF document.getElementById(testdiv).innerHTML = flashMovie; // ExternalInterface.call calls JS but does not return value in IE. Works in FF var tempDiv = document.createElement(div); tempDiv.innerHTML = flashMovie; document.body.appendChild(tempDiv); Here is complete code (ajax.swf can be found in zip files) http://pastebin.com/fbc0aa9a Here is AS3 code in ajax.fla http://pastebin.com/d4efd47b -Heikki -Original Message- From: Mikko Pukki [mailto:mikko.pu...@syncrontech.com] Sent: 4. syyskuuta 2009 15:33 To: users@wicket.apache.org Subject: Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax Hi, This example demonstrates that ExternalInterface fails with IE only if movie is fetched via Wicket/Ajax. ajaxtest.zip: (http://download.syncrontech.com/public/ajaxtest.zip) Page first.html fetches second.html page via Ajax. Second.html has Flash movie that calls JavaScript methods with ExternalInterface and produces output Start... ExternalInterface.available:true ExternalInterface.objectID:testId fromJs:text from js (first.html) This works both FF 3.5 and IE 7/IE8 quickstart_noname.zip: (http://download.syncrontech.com/public/quickstart_noname.zip) Same demonstration with wicket. This fails with IE Start... ExternalInterface.available:true ExternalInterface.objectID:null fromJs:null ObjectId is null and JavaScript call does not return any value. We are aware about EI/IE problems in past, but any of those does not seem to fit here. Wicket 1.4.1, Flash Player 10, IE 7/8, FF 3.5 Has anyone encountered any similar behavior and/or has found any workaround? Should I create a Jira issue? -- Mikko Pukki Syncron Tech Oy Laserkatu 6 53850 Lappeenranta +358 400 757 178 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: How to Show Error Of Page In Deployment MOde
Maybe this helps http://www.nabble.com/How-to-catch-the-error-in-custome-error-page--td9645296.html -Heikki -Original Message- From: carlo c [mailto:carlo.camer...@gmail.com] Sent: 25. helmikuuta 2009 7:16 To: users@wicket.apache.org Subject: How to Show Error Of Page In Deployment MOde hi everyone, I know that this might sound a little strange. but i need to be able to show the error of the system even during deployment mode. I have to show them the stacktrace. The Thing that's preventing us from using development mode is that the application always gets an outofmemoryerror when deployed on websphere. It just shwo internal error. Is there a way that I can override this behavior? carlo -- View this message in context: http://www.nabble.com/How-to-Show-Error-Of-Page-In-Deployment-MOde-tp22196513p22196513.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: textfield to take only numnbers
Pass the field type in the TextField's constructor http://wicketstuff.org/wicket13/compref/?wicket:bookmarkablePage=:org.apache.wicket.examples.compref.TextFieldPage -Heikki -Original Message- From: miro [mailto:miroconn...@yahoo.com] Sent: 29. tammikuuta 2009 17:52 To: users@wicket.apache.org Subject: textfield to take only numnbers I s there any textfield which takes only numbers, I dont want user to enter letters only numbers so I want a textfield which takes only numbers is there any such textfield ? -- View this message in context: http://www.nabble.com/textfield-to--take-only-numnbers-tp21729554p21729554.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: How to get DropDownChoice value without commit form?
Override method wantOnSelectionChangedNotifications :
dropDownChoice = new DropDownChoice...{
@Override
protected boolean wantOnSelectionChangedNotifications() {
return true;
}
@Override
protected void onSelectionChanged(Object newSelection) {
...
}
-Heikki
-Original Message-
From: wch2001 [mailto:wch2...@hotmail.com]
Sent: 30. joulukuuta 2008 9:59
To: users@wicket.apache.org
Subject: How to get DropDownChoice value without commit form?
Dear all,
I have a project to have year dropdown choice (2008,2009, 2010 and so on),
I need its value after it changed but b4 commit the form. How can i do ?
thanks,
Wch2001
--
View this message in context:
http://www.nabble.com/How-to-get-DropDownChoice-value-without-commit-form--tp21214143p21214143.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: feedback message without a form
Refresh feedback panel after setting the message:
final FeedbackPanel feedback = new FeedbackPanel (feedback);
feedback.setOutputMarkupId(true);
add(feedback);
public void onClick(AjaxRequestTarget target) {
if(assignProgramsDTO.getGrantsAssigned().size()==0){
getPage().error(Please assing grants);
target.addComponent(feedback);
return;
}
...
-Heikki
-Original Message-
From: Vance Fellers [mailto:nvfellers...@yahoo.com]
Sent: 30. joulukuuta 2008 21:38
To: users@wicket.apache.org
Subject: Re: feedback message without a form
Have you tried without redirecting to the response page?
miro wrote:
here is my code
public void onClick(AjaxRequestTarget target) {
if(assignProgramsDTO.getGrantsAssigned().size()==0){
getPage().error(Please assing grants);
return;
}
getStgAuditProcessService().startProcess(assignProgramsDTO);
setResponsePage(HomePage.class);
setRedirect(true);
}
miro wrote:
yes
jWeekend wrote:
Did you add a FeedbackPanel to your page?
Regards - Cemal
http://www.jWeekend.co.uk jWeekend
miro wrote:
adding message is simple but how to display this message , who is
rendering the added message ?,
in my case I am adding the message to the page , getPage().info(This
is a test message ) , now what in html i have to do to display this
message ?
James Carman-3 wrote:
Component.info(String message)?
On Mon, Dec 29, 2008 at 12:24 PM, miro miroconn...@yahoo.com wrote:
How to add feed back messages to page with out a form ,
in my case when the link is clicked I call some external service and
that
might return me some message and I want to show this message as a
feedback
message
--
View this message in context:
http://www.nabble.com/feedback-message-without-a-form-tp21206285p21206285.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/feedback-message-without-a-form-tp21206285p21222096.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: Dynamically show and edit a textarea in a table
Hi,
if you put extra div around textarea and add it to the target it should work
final TextArea rejectComment2 = new TextArea(rejectComment2, new
Model(aaa));
rejectComment2.setEnabled(false);
rejectComment2.setVisible(false);
rejectComment2.setOutputMarkupId(true);
final WebMarkupContainer rejectComment2Div = new
WebMarkupContainer(rejectComment2Div);
rejectComment2.setOutputMarkupId(true);
final AjaxFallbackLink enableRejectComment = new
AjaxFallbackLink(enableRejectComment, new Model(
Enable comment textarea )) {
@Override
public void onClick(AjaxRequestTarget target)
{
rejectComment2.setEnabled(true);
rejectComment2.setVisible(true);
target.addComponent(rejectComment2Div);
log.debug(AjaxFallbackLink onClick);
}
};
item.add(rejectComment1);
rejectComment2Div.add(rejectComment2);
item.add(rejectComment2Div);
-Heikki
-Original Message-
From: Claudio Miranda [mailto:clau...@claudius.com.br]
Sent: 29. joulukuuta 2008 3:50
To: users@wicket.apache.org
Subject: Re: Dynamically show and edit a textarea in a table
To let you know, the AjaxEditableMultiLineLabel.onEdit and
AjaxFallbackLink.onClick are called and debug messages logged.
Tried with wicket 1.3.5, same results, no textarea displayed.
Claudio Miranda wrote:
I need to dynamically show a textarea in a row of a table.
The textarea should only be displayed if the user wants to, as he needs to
click at some link.
I developed 2 tests using an AjaxEditableMultiLineLabel and a not visible
textarea. See the runnable code below, to take a look at.
The wicket id is: rejectComment1 and rejectComment2
HTML Code (lines 53 and 60,61)
http://pastebin.com/m2492afac
Java Code (lines 33 and 48)
http://pastebin.com/m490aa72b
But none of them works!
If I click at any of them, the textarea is not displayed.
Are there issues to use them inside a table ?
My system:
Wicket 1.4 RC1
Firefox 3.0.4
Glassfish v2 ur2
Java 6 u11
-
Claudio Miranda
http://weblogs.java.net/blog/claudio
http://www.claudius.com.br/blog
--
View this message in context:
http://www.nabble.com/Dynamically-show-and-edit-a-textarea-in-a-table-tp21197799p21198096.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: Assigning an Action to an onClick handler
Maybe MetaDataRoleAuthorizationStrategy.authorize(link3, Component.ENABLE, ADMIN); -Heikki -Original Message- From: Arie Fishler [mailto:arie@gmail.com] Sent: 18. joulukuuta 2008 16:08 To: users@wicket.apache.org Subject: Assigning an Action to an onClick handler We are using the AnnotationsRoleAuthorizationStrategy class and place @AuthorizeInstantiation(ROLE_USER) on restricted Wicket pages. We need finer-grained authorisation control - we have a class that has 3 AjaxLinks each with their own onClick() handler. 2 of the onClick() handlers are accessible to everyone but 1 requires an authorised user. We have seen it's possible to define a *org.apache.wicket.authorization.Action*class and allocate it to a given role BUT how do we associate the given *Action *to the given onClick() handler? Many thanks Arie - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Assigning an Action to an onClick handler
Maybe something like MetaDataRoleAuthorizationStrategy.authorize(link3, Component.ENABLE, ADMIN); -Heikki -Original Message- From: Arie Fishler [mailto:arie@gmail.com] Sent: 18. joulukuuta 2008 16:08 To: users@wicket.apache.org Subject: Assigning an Action to an onClick handler We are using the AnnotationsRoleAuthorizationStrategy class and place @AuthorizeInstantiation(ROLE_USER) on restricted Wicket pages. We need finer-grained authorisation control - we have a class that has 3 AjaxLinks each with their own onClick() handler. 2 of the onClick() handlers are accessible to everyone but 1 requires an authorised user. We have seen it's possible to define a *org.apache.wicket.authorization.Action*class and allocate it to a given role BUT how do we associate the given *Action *to the given onClick() handler? Many thanks Arie - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
