directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-503) New Entry -> Available object classes list remains stale after new objectclasses added
Date Tue, 21 Jul 2009 23:07:14 GMT


Stefan Seelmann commented on DIRSTUDIO-503:

Damn, there are always problems with schema caching. In general, the schema should be reloaded
if the modifyTimestamp of the schema entry changed.

Could you please check the following:

- Go to Connection Properties -> Connection -> Schema [1]
  - Is the "Modify Timestamp" up-to-date?
  - Is the "Cache Date" newer then the "Modify Timestamp"
  - If possible make a screenshot of this dialog and attach it, please
  - Try to "Reload Schema" and check if the the list now is updated
  - (In case that doesn't help: The schema is cached in an LDIF, you see the location of that
file under "Cache Location", try to delete that cache)


> New Entry -> Available object classes list remains stale after new objectclasses added
> --------------------------------------------------------------------------------------
>                 Key: DIRSTUDIO-503
>                 URL:
>             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
> 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.

View raw message