[
https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733888#action_12733888
]
Graham Leggett commented on DIRSTUDIO-503:
------------------------------------------
Both the create timestamp and modify timestamp are "-", so something is
definitely weird. Ideally if there was a way to selectively disable the cache
that would help a lot during shema development (obviously it wouldn't work for
everybody, my LDAP tree right now is small).
> New Entry -> Available object classes list remains stale after new
> objectclasses added
> --------------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-503
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-503
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0
> Environment: java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
> Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
> Reporter: Graham Leggett
> Attachments: schema-dialog.tiff
>
>
> When an attempt is made to add new objectclasses to a Fedora Directory
> server, these new objectclasses do not show up in the "show available
> objectclasses" dialog during the "new entry" process.
> No obvious functionality exists to force a refresh of this list, or expire
> it's contents.
> The cached objectclass list seems to survive across Eclipse restarts,
> rendering directory studio impossible to use during LDAP schema development.
> A manual query of (cn=schema) shows the new objectclasses as present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
