May be you could provide the developer with access to the page history
utilities such that i can update the version of the current page at will or
leave things to work normally if i dont want to break anything. something
like thisPage.getVersion().increment() ;
regards.
On Fri, Sep 17, 2010 at
the problem with updating the version of the page is that all urls
in the page, be in hrefs or in javascript, have to be rewritten with
the new page version...
-igor
On Tue, Sep 21, 2010 at 2:19 AM, Josh Kamau joshnet2...@gmail.com wrote:
May be you could provide the developer with access to
hello, Is there a way of updating the page version after an ajax request in
order to support the back button for a 100% component based application (i.e
an application based on a single page)?
i think my question is related to this
https://issues.apache.org/jira/browse/WICKET-271.
Has any
, Is there a way of updating the page version after an ajax request in
order to support the back button for a 100% component based application
(i.e
an application based on a single page)?
i think my question is related to this
https://issues.apache.org/jira/browse/WICKET-271.
Has any of the 1.5 milestones
Kamau joshnet2...@gmail.com
hello, Is there a way of updating the page version after an ajax request
in
order to support the back button for a 100% component based application
(i.e
an application based on a single page)?
i think my question is related to this
https://issues.apache.org
On Fri, Sep 17, 2010 at 3:04 PM, Martin Grigorov mgrigo...@apache.org wrote:
I wont say this is a bug.
Actually it is by design.
When the page renders all links' href url points to specific page version.
So when the user clicks on any link the page is properly resolved and the
click
