[
https://issues.apache.org/jira/browse/WICKET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464826
]
Johan Compagner commented on WICKET-201:
----------------------------------------
that page will be saved or not is already covered by 2:
Only save the page when a new version is created (so version 0 == new or
version >0 is in a request later on)
Only one exception.... And that is an ajax request that makes changes to the
version (that i implemented last week)
because ajax does touch now the version info. But doesn't create a new version
but does a merge with the current version.
So when that happens it is a version change (only the version number doesn't go
up) and that is the only situation i can think of
that a page-id:version-id combination needs to be saved again. So normally such
a combination is only saved once.
> refactor storing pages and versions
> -----------------------------------
>
> Key: WICKET-201
> URL: https://issues.apache.org/jira/browse/WICKET-201
> Project: Wicket
> Issue Type: Improvement
> Reporter: Eelco Hillenius
> Assigned To: Johan Compagner
> Fix For: 1.3, 2.0
>
>
> See http://www.nabble.com/refactor-storing-pages-and-versions-tf2943670.html
> for a discussion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
