[ http://issues.apache.org/jira/browse/DIRLDAP-65?page=all ]
Alex Karasulu closed DIRLDAP-65:
--------------------------------
Resolution: Fixed
Committed revision 327982.
http://svn.apache.org/viewcvs.cgi?rev=327982&view=rev
> unrecognized attributes during normalization should not throw exceptions
> ------------------------------------------------------------------------
>
> Key: DIRLDAP-65
> URL: http://issues.apache.org/jira/browse/DIRLDAP-65
> Project: Directory LDAP
> Type: Bug
> Components: Common
> Reporter: Alex Karasulu
> Fix For: 0.9.3
>
> During the normalization process of a DN sometimes its best to not freak out
> and blow a stack trace when an attribute is not recognized. In this case a
> best guess is OK. Let's let the schema handling catch the problem which is
> at a higher level. For now normalized Dn parsers should just leave the value
> as is if the attribute is unrecognized.
> Why is this ok? Again the task of spotting undefined attributes is not the
> job of the DnParser. It should perform a best guess normalization if it can
> using schema info. If this info does not exist the parse should not be
> prevented. This may change in the future when we separate parsing from
> normalization.
> This means we need to check if a NameComponentNormalizer sees an attribute as
> defined or not. If not then we bypass normalization for the value. If so we
> normalize. We need to add an isDefined method to NCN and modify the DnParser
> to adapt to this situation.
--
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
