Hi,
did you find the problem ?
On Fri, May 10, 2013 at 2:33 PM, iamrakesh iamrakes...@rediffmail.comwrote:
Hi,
I did, when the AjaxNewWindowNotifyingBehavior's contructor is called, a
new
value for 'window.name' is generated, but when I see the page source, the
value written to the
Hi,
Nope, didn't had much time today to look into it, probably i've to find out
what is the page id of those two pages [even though they are not added to
the URL], and some debugging.
I'll update this post if I find the issue/solution.
Regards,
Rakesh.A
--
View this message in context:
Hi,
I've a WicketPage implementation to which I've added
AjaxNewWindowNotifyingBehavior, as shown below
public class MyPage extends WicketPage {
public MyPage() {
add(new AjaxNewWindowNotifyingBehavior() {
protected void onNewWindow(AjaxRequestTarget target) {
Hi,
The behavior fires the Ajax call only when the same page instance is loaded
in two tabs/windows.
That is both tabs should have the same pageId in the url query string, e.g.
?3another=parameter, here '3' is the page id.
On Fri, May 10, 2013 at 11:03 AM, iamrakesh
Hi,
I dont have page id in the URL [probably because of
'RenderStrategy.ONE_PASS_RENDER' I've used]!, In this case - is page id
different for pages in two tabs/windows?
If yes, how can I listen to such event?
Regards,
Rakesh.A
--
View this message in context:
Put a breakpoint at the line with: add(new AjaxNewWindowNotifyingBehavior()
{
and another one at
: org.apache.wicket.ajax.AjaxNewWindowNotifyingBehavior#respond()
and see what happens
On Fri, May 10, 2013 at 12:50 PM, iamrakesh iamrakes...@rediffmail.comwrote:
Hi,
I dont have page id in the
Hi,
I did, when the AjaxNewWindowNotifyingBehavior's contructor is called, a new
value for 'window.name' is generated, but when I see the page source, the
value written to the markup is same as the first tab, and the respond method
also gets the same value as the first tab.
Regards,
Rakesh.A
