You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Graham Leggett (JIRA)" <ji...@apache.org> on 2009/07/22 00:49:14 UTC
[jira] Created: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
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
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.
[jira] Updated: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann updated DIRSTUDIO-503:
--------------------------------------
Fix Version/s: 1.5.0
Assignee: Stefan Seelmann
> 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
> Assignee: Stefan Seelmann
> Fix For: 1.5.0
>
> 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Graham Leggett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733894#action_12733894 ]
Graham Leggett commented on DIRSTUDIO-503:
------------------------------------------
Reload schema updated the cache. Is it possible to add this button to dialogs where the schema is present, to force a refersh where necessary?
> 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Graham Leggett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733914#action_12733914 ]
Graham Leggett commented on DIRSTUDIO-503:
------------------------------------------
Using fedora-ds-1.1.3-1.fc6, just checked, there is no modifyTimestamp entry in the schema query.
No problem, glad it wasn't me being dumb.
> 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
> Assignee: Stefan Seelmann
> Fix For: 1.5.0
>
> 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.
[jira] Updated: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Graham Leggett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Graham Leggett updated DIRSTUDIO-503:
-------------------------------------
Attachment: schema-dialog.tiff
Screenshot of the schema dialog
> 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Graham Leggett (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733880#action_12733880 ]
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)
[1] http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_connection_properties.html#tools_connection_properties_schema
> 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
>
> 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.
[jira] Resolved: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann resolved DIRSTUDIO-503.
---------------------------------------
Resolution: Fixed
Fixed in trunk:
http://svn.apache.org/viewvc?rev=822885&view=rev
I added a "reload schema" to the new entry wizard, also fixed the way the schema cache is written.
However I haven't changed the behaviour of automatic schema reloading. If the server's schema doesn't contain a modifyTimestamp (or isn't returned due to access control) then the old cached schema is kept and you need to reload a newer schema manually.
> 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
> Assignee: Stefan Seelmann
> Fix For: 1.5.0
>
> 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.
[jira] Closed: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot closed DIRSTUDIO-503.
--------------------------------------------
Apache Directory studio version 1.5.0 has been released.
> 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
> Assignee: Stefan Seelmann
> Fix For: 1.5.0
>
> 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.
[jira] Commented: (DIRSTUDIO-503) New Entry -> Available object
classes list remains stale after new objectclasses added
Posted by "Graham Leggett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733895#action_12733895 ]
Graham Leggett commented on DIRSTUDIO-503:
------------------------------------------
Reload schema changed the cache date, but modify timestamp remains "-".
> 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.