[
https://issues.apache.org/jira/browse/DIRAPI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908076#comment-13908076
]
Raphaël Ouazana commented on DIRAPI-175:
----------------------------------------
Hi,
I understand your point, put these LDIF with only DN are often returned by LDAP
servers. For example if you search for "1.1" or if you ask only an unknown
attribute. So I think they should be parsed. My goal is not to load them in a
directory, only to be able to parse them easily.
Anyway, as far as I understand it, your parser is not fully compliant with the
BNF, as it allows LDIF without version and empty LDIF. I think it is a good
thing to accept widely used LDIF.
Regards,
Raphaël.
> LdifReader should handle empty entries
> --------------------------------------
>
> Key: DIRAPI-175
> URL: https://issues.apache.org/jira/browse/DIRAPI-175
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M11
> Reporter: Raphaël Ouazana
>
> A simple LDIF file containing 3 entries is rejected by LDIFParser:
> dn: uid=uniqueId, dc=domain
> dn: uid=uniqueId2, dc=domain
> dn: uid=uniqueId3, dc=domain
> I don't see any issue in this LDIF. Parser should return 3 entries with no
> attribute.
> With M11, the error is the following:
> ERROR - ERR_12058_UNKNOWN_ENTRY_TYPE Unknown entry type
> ERROR - ERR_12058_UNKNOWN_ENTRY_TYPE Unknown entry type
> ERROR - ERR_12069 Cannot parse the ldif buffer : ERR_12059_UNKNOWN_ENTRY
> Unknown entry
> ERROR - ERR_12069 Cannot parse the ldif buffer : ERR_12059_UNKNOWN_ENTRY
> Unknown entry
> If I add an attribute to each entry, I get no more error.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
