Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37032DBDA for ; Thu, 4 Oct 2012 00:49:08 +0000 (UTC) Received: (qmail 86197 invoked by uid 500); 4 Oct 2012 00:49:08 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 86137 invoked by uid 500); 4 Oct 2012 00:49:08 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 86124 invoked by uid 99); 4 Oct 2012 00:49:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2012 00:49:07 +0000 Date: Thu, 4 Oct 2012 11:49:07 +1100 (NCT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: <1622836397.163124.1349311747993.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (DIRSHARED-37) Reconsider interfaces and base classes for Registries MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSHARED-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSHARED-37: --------------------------------------- Fix Version/s: (was: 1.0.0-M12) 1.0.0 > Reconsider interfaces and base classes for Registries > ----------------------------------------------------- > > Key: DIRSHARED-37 > URL: https://issues.apache.org/jira/browse/DIRSHARED-37 > Project: Directory Shared > Issue Type: Improvement > Reporter: Alex Karasulu > Priority: Minor > Fix For: 1.0.0 > > > Previously the registries were specifically used by the DS but now they must be used by both studio and the LDAP API. The DS demands strict handling of various schema object dependencies while Studio does not and requires relaxed usage. The LDAP API will have further requirements perhaps, perhaps not. However a couple semantic handling requirements were introduced into the Registries to make them handle these various cases (relaxed verses strict usage). Rather than leaving these semantics in a single implementation we should instead reconsider splitting the implementation and re-exposing interfaces to use different implementations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira