[DIRSTUDIO-503] New Entry -> Available object classes list remains stale after new objectclasses added

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: studio-ldapbrowser
• 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)
• Assignee: Stefan Seelmann
• Reporter: Graham Leggett
• Created: 21/Jul/09 22:47
• Updated: 19/Nov/09 15:39
• Resolved: 07/Oct/09 20:10

Description

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.