directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve hammond (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-1586) 2.0 does not have a way to load external Ldifs (h.350)
Date Tue, 30 Nov 2010 17:40:11 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve hammond updated DIRSERVER-1586:
-------------------------------------

    Attachment: XmppURIObject.ldif
                commObject.ldif

here are 2 sample files, i have all of H.350 and a couple proprietary ones.

> 2.0 does not have a way to load external Ldifs (h.350)
> ------------------------------------------------------
>
>                 Key: DIRSERVER-1586
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1586
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0
>         Environment: Running on windows XP and Windows 2003 server
>            Reporter: Steve hammond
>         Attachments: commObject.ldif, XmppURIObject.ldif
>
>
> We need a method that is consistent with ldif files exported from Apache directory Studio,
that can be loaded to extend the schema of our server.
> In 1.5.3 I did ApacheDS.setLdifDirectory, then when the LDAP server started, it imported
and used the ldif definitions in that directory.  I have exhausted all methods I could find
to load these LDIF files.
> I tried ApplyLdifs, but that takes a description parameter that is part of Junit, not
real good for production code, and the Description I can get out of Junit does not have the
getAnnotation method on it.
> I tried DSAnnotationProcessor.injectLdifFiles directly, but it could never open the file
names i gave it.
> I tried writing my own injectLdifFiles method, but always got an error when trying to
add attributes to an objectclass that I had just added, saying that this objectClass is not
yet loaded.
> I tried making my own implementation of AbstractSchemaLoader, but that pukes saying that
all schemas must have a valid creatorsName attribute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message