Thanks for the reference. This is exactly what I want!
Regards
Robin
From: Martin Grigorov
To: "users@wicket.apache.org" ; Robin Shine
Sent: Thursday, September 18, 2014 11:53 PM
Subject: Re: Expire page upon session timeout
Hi,
>From ye
Hi,
When an ajax link is clicked after session is timed out, Wicket 1.6 now
refreshes the page silently instead of throwing the PageExpiredException. This
sometimes causes confusions and even can lead to page being refreshed
incorrectly with wrong query parameters. To avoid the confusion, I'd
if page constructor throws an
exception
Hi Robin,
we should try to improve that. Please create a new issue with a quickstart.
Thanks
Sven
On 03/28/2014 09:16 AM, Robin Shine wrote:
> Hi Sven,
>
> Thanks for looking into this. I started a new wicket project from scratch
> using
From: Sven Meier
To: users@wicket.apache.org
Sent: Thursday, March 27, 2014 10:49 PM
Subject: Re: Avoid calling Page.onInitialize if page constructor throws an
exception
Hi,
#onInitialize() is not called here with 6.14.0 and 6.15.0-SNAPSHOT.
Regards
Sven
On 03/27/2014 03:30 PM, Robin Shine
Hi All,
We are glad to see that the issue WICKET-5387 (Page#onInitialize called after
an exception in the constructor of Page) has been resolved in 6.13.0. However
when I tried this version (and 6.14.0) with below code, the issue still exist:
public class TestPage extends WebPage {
public
: "users@wicket.apache.org"
Date: Tuesday, June 11, 2013, 7:05 PM
Hi,
On Tue, Jun 11, 2013 at 1:23 PM, Robin Shine wrote:
> Hi All,
>
> We are using Wicket to develop our web application product (QuickBuild)
> for six years, and this makes our life a lot easier when comes to ma
patch didn't make it through to the mailing list, and things
tend to get lost anyway due to the amount of traffic on this list.
Martijn
On Tue, Jun 11, 2013 at 12:23 PM, Robin Shine wrote:
> Hi All,
>
> We are using Wicket to develop our web application product (QuickBuild)
> f
Hi All,
We are using Wicket to develop our web application product (QuickBuild) for six
years, and this makes our life a lot easier when comes to maintain our code
base due to Wicket's component approach and type safe nature of Java.
As our product gets more used in companies, it is not uncom
onent's model changes.
>>
>> On Wed, Dec 7, 2011 at 8:24 PM, Robin Shine wrote:
>>
>> > Hi All,
>> >
>> >
>> > In Wicket 1.5.3, I create a very simple page containing a label and a
>> > link, when the link is clicked, it increases a c
Hi Dan,
Thanks for the quick response. The dirty() method does make the back button
work again.
Regards
Robin
From: Dan Retzlaff
To: users@wicket.apache.org; Robin Shine
Sent: Thursday, December 8, 2011 1:57 PM
Subject: Re: Back button not work in
Hi All,
In Wicket 1.5.3, I create a very simple page containing a label and a link,
when the link is clicked, it increases a counter, and change model value of the
label. Thus the counter on the page will increase each time the link is
clicked. For instance, the initial value displayed is 0,
Subject: Re: Page.onPageAttached() never gets called in 1.5?
To: users@wicket.apache.org
Cc: "Robin Shine"
Date: Tuesday, March 8, 2011, 12:02 AM
i dont seem to understand the entire usecase here, if you are running
code inside a listener then you can get page via getpage()...
-igor
On
Robin
--- On Mon, 3/7/11, Igor Vaynberg wrote:
From: Igor Vaynberg
Subject: Re: Page.onPageAttached() never gets called in 1.5?
To: users@wicket.apache.org
Cc: "Robin Shine"
Date: Monday, March 7, 2011, 1:27 PM
i think this method should be removed from Page, for code that need
Hi All,
We rely on this method to store the page instance being processed into a thread
local so that we can easily get current page even from component constructors.
In 1.4 this method is invoked after page is retrieved from session store for
example when click an ajax link on the page. Howeve
-- Tony
On Thu, Mar 19, 2009 at 4:04 PM, Leszek Gawron wrote:
> Robin Shine wrote:
>>
>> Hi All,
>> It seems that the navigation toolbar of data table component can not be
>> displayed if there is a link on the page surrounded with the
>> wicket:encl
: Leszek Gawron
Subject: Re: Wicket:enclosure does not work with navigation toolbar of data
table
To: users@wicket.apache.org
Date: Thursday, March 19, 2009, 5:04 PM
Robin Shine wrote:
> Hi All,
> It seems that the navigation toolbar of data table component can not be
> displayed if t
Hi Matt,
Thanks for your quick answer. Although in this simple case, it is enough to
only update the count label. However in my application, it is necessary to
update the whole region including the component initiating the ajax action. One
scenario is that I've written a treetable component
The test page is rather simple, I will paste it here:
TestPage.java:
package com.pmease.quickbuild.test;
import org.apache.wicket.ajax.AjaxRequestTarget;
import org.apache.wicket.ajax.markup.html.AjaxLink;
import org.apache.wicket.behavior.HeaderContributor;
import org.apache.wicket.markup.html.
Hi All,
I am facing with a strange issue that the Ajax postcall handler (registered
with Wicket.Ajax.registerPostCallHandler) is only called for the first time
when browser is closed and opened again, and subsequent calls does not trigger
the handler. To reproduce this, please copy the attache
s back button and clicks
a ling to page, it will
affect the previous page version. Wicket takes care of this
automatically. Can you keep the state in page instead of keeping it in
session?
-Matej
On Jan 10, 2008 11:29 AM, Robin Shine wrote:
> Hi,
>
> I am facing a situation where I need t
Hi,
I am facing a situation where I need to rollback some state kept in session
when user hits the back button at browser side, and clicks some link which
triggers a server round trip. The usage scenario is as below:
1. User stays on page1, and the current state saved in session in state1
2. Us
21 matches
Mail list logo
