On Tue, Jul 13, 2010 at 3:02 PM, Mike Müller <[email protected]> wrote: >> If you need to maintain related nodes B after saving a node A, the >> recommended way with JCR is to use observation: you'll get a callback >> when A is modified, and you setup B at this point, asynchronously. > > What would you suggest if saving of node B should be done transactionally?
You'd then need to implement custom code (POST handler or servlet) to save A and update B transactionally. Event listeners are called asynchronously after the observed node is saved. Or use a temporary "incoming" path for the A node, and in the listener update B and move A to its final location in a transaction. -Bertrand
