[
https://issues.apache.org/jira/browse/DIRSERVER-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-953:
----------------------------------------
Fix Version/s: (was: 1.5.2)
2.0.0
A bit too complex for the 1.5.3.
> Provide registration scope support for Subtree (besides current Base support)
> in ModifyDN.Export/Import Triggers
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-953
> URL: https://issues.apache.org/jira/browse/DIRSERVER-953
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.5.0
> Reporter: Ersin Er
> Assignee: Ersin Er
> Priority: Minor
> Fix For: 2.0.0
>
>
> Current implementation of Trigger System allow registering Triggers for
> ModifyDN.Export/Import operations on only the base entry which the request is
> made on. However, in a MoveAndRename operation, more than one entries are
> affected (moved). So it may be needed to handle each moved entry within a
> Stored Procedure.
> The support for an optional Subtree scope in ModifyDN Triggers can be
> provided by executing the Stored Procedure with new set of operation specific
> parameters for each moved entry. So for example the $newSuperior will be
> calculated differently for each entry which the SP is called with respect to.
> Following is an example of proposed extension:
> AFTER ModifyDN.Export:Subtree CALL "logger.LogMove" ($newDN, $entry);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
