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/13 09:37:00 UTC
[jira] [Updated] (DIRSTUDIO-1228) Automatically update the
SchemaManager of a connection for which the schema has been changed
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSTUDIO-1228:
-----------------------------------------
Description:
When connected to an {{ApacheDS}} instance, and if we change the schema (like if we enable the {{NIS}} schema), adding an entry using one of the {{NIS}} schema {{ObjectClass}} does not show the updated schema, we need to reload it using the special button on the {{New Entry}} popup. This is not very convenient. It would be cool to have the local SchemaManager}} being updated automatically when the remote {{ApacheDS}} server schema has been updated (something that we know because we have updated this schema).
If updating the {{SchemaManager}} can be problematic, then asking if {{Studio}} should update it when a schema element has been changed could be an option (if we touch the {{ou=schema}} content, a popup like {{"Would you updated the local SchemaManager yes/no}}" could be valuable)
was:
When connected to an {{ApacheDS}} instance, and if we change the schema (like if we enable the {{NIS}} schema), adding an entry using one of the {{NIS}} schema {{ObjectClass}} does not show the updated schema, we need to reload it using the special button on the {{New Entry}} popup. This is not very convenient. It would be cool to have the local SchemaManager}} being updated automatically when the remote {{ApacheDS}} server schema has been updated (something that we know because we have updated this schema).
If updating the {{SchemaManager}} can be problematic, then asking if {{Studio}} should update it when a schema element has been changed could be an option (if we touch the {{ou=schema}} content, a popup like {{"Would you updated the local SchemaManager}} yes/no}} could be valuable)
> Automatically update the SchemaManager of a connection for which the schema has been changed
> --------------------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-1228
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1228
> Project: Directory Studio
> Issue Type: Improvement
> Components: studio-ldapbrowser
> Affects Versions: 2.0.0-M14
> Reporter: Emmanuel Lecharny
> Priority: Major
>
> When connected to an {{ApacheDS}} instance, and if we change the schema (like if we enable the {{NIS}} schema), adding an entry using one of the {{NIS}} schema {{ObjectClass}} does not show the updated schema, we need to reload it using the special button on the {{New Entry}} popup. This is not very convenient. It would be cool to have the local SchemaManager}} being updated automatically when the remote {{ApacheDS}} server schema has been updated (something that we know because we have updated this schema).
> If updating the {{SchemaManager}} can be problematic, then asking if {{Studio}} should update it when a schema element has been changed could be an option (if we touch the {{ou=schema}} content, a popup like {{"Would you updated the local SchemaManager yes/no}}" could be valuable)
--
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