cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Fiol (JIRA)" <>
Subject [jira] Commented: (COCOON-1775) LdapTransformer: LDAP attributes may not contain ";"
Date Sat, 25 Feb 2006 09:21:40 GMT
    [ ] 

Antonio Fiol commented on COCOON-1775:

I will try, but don't expect it in less than one week. I'm overloaded at the moment. I'll
take the second approach if nobody asks otherwise.

> LdapTransformer: LDAP attributes may not contain ";"
> ----------------------------------------------------
>          Key: COCOON-1775
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Naming
>     Versions: 2.1.8
>     Reporter: Antonio Fiol
>     Assignee: Jean-Baptiste Quenot

> I found a case where the LDAP attribute name is:
> description;lang-en
> LDAPTransformer tries to create an element such as:
> <ldap:description;lang-en>something</ldap:description;lang-en>
> This is not valid XML and causes an exception.
> In fact, this attribute naming scheme complies both with RFC 2596 [1] and RFC 2252 [2],
so the behaviour of LDAPTransformer is somehow wrong.
> Three possible approaches:
> - Investigate further on the meaning of name;something other than name;lang-something
and try to map that into meaningful XML attributes.
>     e.g. description;lang-en --> <ldap:description xml:lang="en">
> - Split the attribute name at the first ";" and put the rest as an attribute. For example,
the attribute could be called "attrs".
>     e.g. description;lang-en --> <ldap:description attrs="lang-en">
> - Remove the ";" character or change it into something else.
>     e.g. description;lang-en --> <ldap:description_lang-en>
> IMHO the third approach is the worst because it defeats the LDAP purpose of ";" which
is to specify a characteristic of what is specified before. And I don't have a strong opinion
whether the first approach is better than the second or vice-versa.

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