Currently, each XWiki document modification creates a new version of that document: the save and continue action, adding/deleting objects or class properties, etc. In the end, most documents will end up with a lot of versions that should not be visible in the document's history because they constitute work in progress and are not informative by themselves. Additionally, the results of actions like adding or deleting an object from the object editor do not disappear when canceling the edit, which may create confusion for unexperienced users.

A possible solution to these issues are pseudoversions. Pseudoversions are temporary versions of a document being edited, and can be seen as short-lived versioning branches, resulting in a one official version when the user finishes editing the document.

A chain of pseudoversions is tied to a user, meaning that by default the user's changes are saved as pseudoversions in a private branch. When the user finishes editing the page by clicking "save", the last pseudoversion is saved as a full version, and the branch is deleted.

In addition to giving an answer to the problems listed above, pseudoversions created regularly during document editing can serve as a back-up system, so that users can recover unsaved work in case of a browser crash or other types of accidents that may cause data loss. 

See also:

Developer profile

Strong knowledge of Java, and ORM (hibernate)






Get Connected