directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbert Reilly (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-604) Support for ":<" LDIF syntax in ApacheDS
Date Thu, 30 Mar 2006 01:51:42 GMT
    [ ] 

Norbert Reilly commented on DIRSERVER-604:

I have a new patch but can't remove the existing attachments (all should be removed and replaced
with single latest patch).

I found my fix worked fine for binary attributes to be stored in the Attribute object as a
byte[], but my particular interest was in a string field.

Hence the new patch includes support for an extension of the rfc2849  support to handle a)
specifying the value read from the URL should be treated as a String and b) if so, then specifying
what its encoding is. For example the following are all valid (contents of attached test .ldif

    # attribute is stored as byte[]
    httpurl:< http://isis/public/hopno02/jx.txt

    # attribute is stored as byte[]
    fileurl:< file:///D:/src/ad/shared/ldap/src/test/resources/test_ldif_inclusion.txt

    # attribute is stored as UTF8 encoded String
    strfileurl:< string_encoding=UTF8;file:///D:/src/ad/shared/ldap/src/test/resources/test_ldif_inclusion.txt

where the "string_encoding=<encoding>;" bit is not part of the RFC. I can't see anywhere
in the RFC where this sort of issue is dealt with. Access to the schema for each attribute
would help in knowing what the directory view of it is, but still won't address the issue
of the encoding for the file being read.

Any guidance welcomed...

> Support for ":<" LDIF syntax in ApacheDS
> ----------------------------------------
>          Key: DIRSERVER-604
>          URL:
>      Project: Directory ApacheDS
>         Type: New Feature
>   Components: ldap
>  Environment: N/A
>     Reporter: Norbert Reilly
>  Attachments: rfc2849 _inclusion_support.patch, rfc2849 _inclusion_support.patch, test_inclusion.ldif,
> I have need to import potentially long files via LDAP and noted that
> rfc2849 mentioned the ":<" operator allowing an attribute's value to
> be provided by "including" the contents of a URL.
> I have added the support for ":<" by enhancing
> in
> trunks/shared/ldap .

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message