On 6 May 2009, at 16:17, Carsten Ziegeler wrote:
Ian Boston wrote:
Agreed,
the reason for sharing this is we have some use cases that need to
look
at the node state prior to save. In the past (pre OSGi) we added
these
to the the jcr server component. Since this is now owned by Sling, we
cant do that any more without patching the jackrabbit-server bundle.
Obviously there needs to be a hook somewhere for this use case to be
covered.
The more generic event use case *is* better handled by the OSGi event
service, especially where delivery is not expected to be on the same
thread or even on the same cluster node.
I could make this patch only for SynchronousEventsListeners.
WDYT?
Not sure :) You mention that you want to look at the node state
prior to
save,
so maybe the SlingPostProcessor (post bundle) can help you? You can
register these processors and they are invoked on a POST to Sling
before
the save is called. It allows you to make additional changes, revert
them etc.
yes this would work for the cases where standard POSTS were made,
there are instances where we have services, that are exposed as either
JAX-RS or Sling POST Servlets.
Question:
Would we see all the nodes modified in this case, or just the ones
that are referenced by the POST operation (eg a POST modifies 10 nodes
scattered around the repo).
Ian
Carsten
--
Carsten Ziegeler
cziege...@apache.org
