[
https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733898#action_12733898
]
Stefan Seelmann commented on DIRSTUDIO-503:
-------------------------------------------
Seems like FedoraDS (389DS) doesn't provide a modifyTimestamp for the schema.
Do you see a modifyTimestamp in the "cn=schema" entry?. Which version of
FedoraDS are you using?
I checked the code and there is an bug: If the both createTimestamp and
modifyTimestamp are null then the schema is _not_ reloaded automatically. I'll
correct that. Thanks for the report.
> 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.
