Destination in ABOUT_TO_MOVE and ABOUt_TO_COPY events

How come the destination is not available while handling those events?

This makes it impossible to implement a reliable integrity enforcement policy, waiting for the CREATED event means having a possibly corrupt or incomplete document available to other handlers.

The information is readily available in AbstractSession when notifyEvent is called, is there any reason for not including the destination in the event context (or at least in the context's properties)?


0 votes

1 answers



There's no good reason for them to be missing. Please open a NXP ticket to request this enhancement.

0 votes