You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/05/26 14:26:54 UTC
[jira] Updated: (DIRSERVER-1370) Improve the schema handling
[ https://issues.apache.org/jira/browse/DIRSERVER-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1370:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> Improve the schema handling
> ---------------------------
>
> Key: DIRSERVER-1370
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1370
> Project: Directory ApacheDS
> Issue Type: Task
> Components: schema
> Reporter: Kiran Ayyagari
> Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> excerpts from the IRC with Emmanuel
> <ayyagari> btw, the schema loading seems to be a bit heavy thing
> <ayyagari> so I relied completely on DefaultDirectoryService class to get access to registries
> <elecharny> yeah, the schema handling part might deserve a rewrite :)
> <elecharny> we discussed shortly about it with Alex yesturday
> <elecharny> what I would love to see is a system allowing the server
> <elecharny> to load the server from .schema files
> <elecharny> without having all this plugins generating code for nothing
> <ayyagari> that would be a great improvement IMHO
> <elecharny> yeah
> <elecharny> the idea is to check if the .schema files has been changed
> <elecharny> maybe we should also create a JIRA for this schema rewrite
> <elecharny> probably necessary for 2.0
> <elecharny> if we can get rid of those two plugins (maven plugins),
> <elecharny> that would be just great
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.