On Mon, 11 Feb 2008 13:01:47 +0100
Johan Compagner [EMAIL PROTECTED] wrote:
i guess we could up the level a bit yes
Because in 1.3 it is pretty serious error if we cant save the page.
Great! Should I open a JIRA issue to track this?
On Sat, 9 Feb 2008 09:51:45 +0100
Johan Compagner [EMAIL PROTECTED] wrote:
What wicket version is this?
Normally in 1.3 page expires should never happen, except when your
page isnt serializeble...
Here it is! My page wasn't serializable, but my Logback configuration hid the
exception.. :(
i guess we could up the level a bit yes
Because in 1.3 it is pretty serious error if we cant save the page.
johan
On Feb 11, 2008 11:11 AM, Federico Fanton [EMAIL PROTECTED] wrote:
On Sat, 9 Feb 2008 09:51:45 +0100
Johan Compagner [EMAIL PROTECTED] wrote:
What wicket version is this?
What wicket version is this?
Normally in 1.3 page expires should never happen, except when your
page isnt serializeble...
On 2/8/08, Federico Fanton [EMAIL PROTECTED] wrote:
Hi everyone!
I'm looking for a little help please..
I have a search page with a form and a custom DataTable (with
Hi everyone!
I'm looking for a little help please..
I have a search page with a form and a custom DataTable (with
SortableDataProvider).
Everything works fine: I can set filters from the form, order the table by
clicking on column headers, browse through the table pages, etc.. My problem is
If I recall correctly we had a similar problem a little while ago.
As it turned out the page was requested twice but only the first was rendered.
The reason the page was requested twice was because we had something
like this on our page img src /
For some reason the absence of a valid source tag
second level session store holds x number of previous versions. some
implementations like disk store hold quiet a few versions.
i cant reproduce your error here:
http://wicketstuff.org/wicket13/repeater/?wicket:bookmarkablePage=%3Aorg.apache.wicket.examples.repeater.DataTablePage
can you try?
On Fri, 8 Feb 2008 12:50:34 +0100
Federico Fanton [EMAIL PROTECTED] wrote:
My problem is that if I _quickly_ doubleclick
on a column header (even with no data in the table),
I get a PageExpiredException. I tried debugging
this, so I saw that WicketServlet receives two
calls, and the second
On Fri, 8 Feb 2008 15:49:58 +0100
Maurice Marrink [EMAIL PROTECTED] wrote:
If I recall correctly we had a similar problem a little while ago.
As it turned out the page was requested twice but only the first was rendered.
The reason the page was requested twice was because we had something
