Hi List,
Has anyone an idea on this topic:
Versioning for Audit Trail.
I understand from JackRabbit's docs that after you add the
versionable "mixin", nodes, upon a change, get a new version nr.
The questions I have with this, are:
1/ How to best ALSO capture WHO made the change and WHY? (so
basically add to Strings to a version @ each version increment)
Do I just add the fields to the "content" node (e.g. for a Book node
being under version control: add a "UID" & "Reason" property, both
also faturing the versionable mixin) or is it possible to somehow
extend the Version Node itself with these extra 2 fields?
In the latter case, this would substantially reduce the efforts to
also audit trail other nbodes + be less invasive. (original Nodes are
left untouched)
2/ Is the versioning schema controllable? I mean: what happens if
subnode B of Supernode A is changed from v3 to version 4.
Is the Supernode version then NOT changed, or does it get a change
like A (v2) --> A (v2.1) etc...?
I'm sure you can imagine lots of other schemas. So: Which one is
followed by default & is this configurable?
3/ For the authorization part: any recommendtions on whether to use
JAAS or Acegi? (using Spring anyway so not much extras to setup acegi
if there are advantages over JAAS)
Thx for all help!
Wolf
