| Emmanuel Lecharny (JIRA) 2007-04-21, 7:11 am |
|
[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-297.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> NormalizationService is failing to parse escaped names
> ------------------------------------------------------
>
> Key: DIRSERVER-297
> URL: https://issues.apache.org/jira/browse/DIRSERVER-297
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Giamma
> Assigned To: Alex Karasulu
>
> I wrote a custom partition to extract data from our oracle database.
> Some of the names returned from out db needs to be escaped because they have special chars like: "," "/" and "="
> This is done using LdapName.escapeAttributeValue().
> Unfortunately the DnParser (in NormalizationService) is not doing the right thing when processing these escaped names.
> I had to change the code in NormalizationService to still call the parser (to check invalid DN syntax) but I skipped
> using the text returned by the parser because it would remove spaces after an escaped ","
> Let's say I have a RDN like this:
> "ou=some test, something else"
> After I escaped it it wil be like this:
> "ou=some test\\, something else"
> The parser will remove the space after the escaped ","
> "ou=some test\\,something else"
> And that breaks the code in my custom partition because it's not finding the right object.
> Here is the fix I made.
> But it's just an hack. I think the problem is in the DnParser. But I do not have the source for that.
> protected void process( NextInterceptor nextInterceptor, Delete call ) throws NamingException
> {
> synchronized( parser )
> {
> // call.getName( parser.parse( call.getName().toString() ) );
> // call it anyway to catch invalid DN syntax
> parser.parse( call.getName().toString() );
> }
> super.process( nextInterceptor, call );
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|