You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/06/30 05:31:01 UTC
[jira] [Updated] (DIRSERVER-433) Complete support for most schema
checking constructs
[ https://issues.apache.org/jira/browse/DIRSERVER-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-433:
----------------------------------------
Component/s: (was: core)
schema
adminRole
> Complete support for most schema checking constructs
> ----------------------------------------------------
>
> Key: DIRSERVER-433
> URL: https://issues.apache.org/jira/browse/DIRSERVER-433
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: adminRole, schema
> Reporter: Enrique Rodriguez
> Priority: Major
> Fix For: 2.1.0
>
>
> Everything is in place for schema checking but nothing exists today. The reason being Alex did not waste time on schema subsystem since it would need to be revamped once we implemented subentries. Subentries for schema AAAs would store the schema info there rather than having one schema for the entire DIT mastered by a DSA. Basically an interceptor for schema management would use the subentry information to check for correct schema usage in different schema AAAs in the DIT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org