Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <2845583.1188090810649.JavaMail.jira@brutus>
Date: Sat, 25 Aug 2007 18:13:30 -0700 (PDT)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSERVER-1030) Add CascadeControl and add
 functionality to cascade modify and delete effects
In-Reply-To: <29770781.1187883630488.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-1030:
-------------------------------------

    Affects Version/s:     (was: 1.5.0)
                       1.5.1
                       1.5.2
        Fix Version/s:     (was: 1.5.1)
                       1.5.3

The control was added for the protocol and made to tunnel down into the core of the server with various changes committed for this issue.  However after some discussion the needs of the Directory studio product seemed not to require this modification however the control can still be implemented later on since it does server a purpose.  However there is no urgency for it so we're moving it out to another release.

> Add CascadeControl and add functionality to cascade modify and delete effects
> -----------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1030
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>    Affects Versions: 1.5.2, 1.5.1
>            Reporter: Alex Karasulu
>             Fix For: 1.5.3
>
>
> We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes.  The behavior of the control is context specific.  This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.