Provide more sophisticated listener mechanism in addition to JCR observation API
--------------------------------------------------------------------------------
Key: JCR-2101
URL: https://issues.apache.org/jira/browse/JCR-2101
Project: Jackrabbit Content Repository
Issue Type: New Feature
Components: jackrabbit-core
Affects Versions: 1.5.5
Reporter: Alfie Kirkpatrick
The current observation API in JCR has the problem that when nodes/properties
are removed it is not possible to look at the state of the items before
removal. All you get is the path which has already been removed. In a similar
fashion to db triggers it should be possible to hook into change events at a
very low level, eg. beforeRemove, beforeChange, beforeAdd.
Currently there are many different ways nodes/properties can be created,
changed and destroyed, eg. by import, version restore, etc, etc. This makes it
very hard if not impossible to wrap this listener framework around the current
Jackrabbit code.
I realise there is a potential issue with operations outside any session, eg.
Workspace.importXML. I think most applications could probably live with the
limitation that changes are only tracked if made via a session.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
