cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Baptiste Quenot (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-1775) LdapTransformer: LDAP attributes may not contain ";"
Date Tue, 03 Oct 2006 08:04:21 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1775?page=all ]

Jean-Baptiste Quenot closed COCOON-1775.
----------------------------------------

    Resolution: Won't Fix

Please reopen the issue if you can come up with a patch.  Thanks!

> LdapTransformer: LDAP attributes may not contain ";"
> ----------------------------------------------------
>
>                 Key: COCOON-1775
>                 URL: http://issues.apache.org/jira/browse/COCOON-1775
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Naming
>    Affects Versions: 2.1.8
>            Reporter: Antonio Fiol
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message