BgiframeJavaScriptResourceReference in wicket 6.5.0

Hi, I am trying upgrade wicket library version from 1.4.21 to 6.5.0. I am using BgiframeJavaScriptResourceReference class and I couldn't find it in the latest version and couldn't find any text in migration Wiki page! Is there any replacement for this class? Regards, Rakesh.A -- View this

Re: BgiframeJavaScriptResourceReference in wicket 6.5.0

:46 PM, iamrakesh lt; iamrakesh22@ gt;wrote: Hi, I am trying upgrade wicket library version from 1.4.21 to 6.5.0. I am using BgiframeJavaScriptResourceReference class and I couldn't find it in the latest version and couldn't find any text in migration Wiki page! Is there any replacement

Migrating WebRequestCycleProcessor from 1.4.x to 6.5.0

Hi, I am trying migration code from wicket v1.4 to v6.5.0, I've a custom implementation of WebRequestCycleProcessor, on migration wiki page I read that WebRequestcycleProcessor is removed, is there any replacement for this class? Regards, Rakesh.A -- View this message in context:

Re: Migrating WebRequestCycleProcessor from 1.4.x to 6.5.0

Hi, In resolve() method we're trying to catch handle InvalidUrlException to prevent exception due to multiple clicks on a button. In respond() method we're logging the request target [RequestCycle#getRequestTarget() value] and if it is of type AjaxRequestTarget we're trying to add components to

Problem with window name generated using AjaxNewWindowNotifyingBehavior in wicket 6.5.0

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) {

Re: Problem with window name generated using AjaxNewWindowNotifyingBehavior in wicket 6.5.0

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:

Re: Problem with window name generated using AjaxNewWindowNotifyingBehavior in wicket 6.5.0

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

Re: Problem with window name generated using AjaxNewWindowNotifyingBehavior in wicket 6.5.0

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:

Problem with AjaxRequestTarget.AbstractListener org.apache.wicket.extensions.markup.html.tree.Tree

Hi, We've recently upgraded to v6.5.0 [from 1.4.21]; we've implementation of Tree class which is now deprecated [we're still using the deprecated tree implementation - for now]. Earlier we used a custom WebRequestCycleProcessor and in the respond() method we did some cleanup related to the

Re: Problem with AjaxRequestTarget.AbstractListener org.apache.wicket.extensions.markup.html.tree.Tree

Hi, Yes, we registered the listener like below getAjaxRequestTargetListeners().add(new AjaxRequestTarget.AbstractListener() { @Override public void onBeforeRespond(MapString, Component aMap, AjaxRequestTarget aTarget) { } }); I'll try to create a

CryptoMapper not encoding query string - Wicket 6.5.0

Hi, I am using Wicket 6.5.0 and I am trying to use CryptoMapper in my application and URLs in my application look something like the one given below

Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

Hi, In Wicket 1.4.x org.apache.wicket.Page.componentChanged(Component, MarkupContainer) is called every time a component gets changed, it seems it is not being called anymore in wicket 6.5.0. Is there any alternative for this method? Is there any way to listen for event when a component is