As a followup question
Until this bug has been fixed, is there a way to disable page versioning
all-together? My app is very ajax heavy, so it's bordering on unusable
until this is fixed.
On 1/17/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
Done!
in your page call setversioned(false)
-igor
On 1/21/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
As a followup question
Until this bug has been fixed, is there a way to disable page versioning
all-together? My app is very ajax heavy, so it's bordering on unusable
until this is fixed.
On
Yeah, this is a problem with 2.0 currently. Ajax requests increase page
version. Johan promised to fix this soon :)
-Matej
Igor Vaynberg wrote:
a good start is to isolate this in a quickstart so we can all look at
it. if you want to do it yourself then just break in request cycle and
walk
dont think so but feel free to open one
-igor
On 1/17/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
Thanks for the update.
is there a JIRA issue that I can watch for when this will be fixed?
On 1/17/07, Matej Knopp [EMAIL PROTECTED] wrote:
Yeah, this is a problem with 2.0 currently. Ajax
Thanks for the update.
is there a JIRA issue that I can watch for when this will be fixed?
On 1/17/07, Matej Knopp [EMAIL PROTECTED] wrote:
Yeah, this is a problem with 2.0 currently. Ajax requests increase page
version. Johan promised to fix this soon :)
-Matej
Igor Vaynberg wrote:
a good
Done!
https://issues.apache.org/jira/browse/WICKET-216
On 1/17/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
dont think so but feel free to open one
-igor
On 1/17/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
Thanks for the update.
is there a JIRA issue that I can watch for when this will be
I'm running wicket-2.0 from a recent svn checkout and i'm seeing a *lot* of
page expired exceptions when using ajax behaviors. I'm wondering where I
can start digging to see why this is happening. Any ideas?
-
Take Surveys.
