directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRAPI-114) Reconsider interfaces and base classes for Registries
Date Thu, 24 Sep 2015 15:33:04 GMT

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

Emmanuel Lecharny resolved DIRAPI-114.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-M32

Actually, we now have a relaxed mode that works well even for schema that are not consistents.
This should be ok for ApacheDS or other LDAP servers.

> Reconsider interfaces and base classes for Registries
> -----------------------------------------------------
>
>                 Key: DIRAPI-114
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-114
>             Project: Directory Client API
>          Issue Type: Bug
>            Reporter: Alex Karasulu
>            Priority: Minor
>             Fix For: 1.0.0-M32, 1.0.0-RC1
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message