Le 16/09/15 14:13, GATTAZ Olivier a écrit :
> Bonjour,
>
> No, I don’t test this feature with M20 because we downgrade ADS from M20 to
> M14 according the fact we have many problems with the management of the
> aliases… :-(
What kind of problem do you have with aliases ? Are there any JIRA that
we need to fix ?
>
> My colleague using windows doesn’t have problem giving the value « E:/ ». The
> journal file is created at the right place...
Hmm...
I have checked the code that controls the PrintableString values, and it
hasn't changed in 3 years. I have added a quick test :
@Test
public void testPath()
{
assertTrue( checker.isValidSyntax( "/" ) );
assertTrue( checker.isValidSyntax( "E:/" ) );
assertTrue( checker.isValidSyntax(
"/Users/me/workspaces/projects/myProject/ldap/" ) );
}
All three tests are green.
The error message is produced in this piece of code :
// Check the syntax
if ( !isValid( syntax.getSyntaxChecker() ) )
{
String message = I18n.err(
I18n.ERR_04473_NOT_VALID_VALUE, wrappedValue, attributeType );
LOG.info( message );
throw new LdapInvalidAttributeValueException(
ResultCodeEnum.INVALID_ATTRIBUTE_SYNTAX, message );
}
and the isValid( syntax.getSyntaxChecker() ) will return false only when
the following method returns false :
public final boolean isValid( SyntaxChecker syntaxChecker ) throws
LdapInvalidAttributeValueException
{
if ( syntaxChecker == null )
{
String message = I18n.err( I18n.ERR_04139, toString() );
LOG.error( message );
throw new LdapInvalidAttributeValueException(
ResultCodeEnum.INVALID_ATTRIBUTE_SYNTAX, message );
}
return syntaxChecker.isValidSyntax( normalizedValue );
}
As the syntaxChecker.isValidSyntax( normalizedValue ) will return true,
the only possible error is that the syntaxChecker is null, but in this
case, you'll get a different error message :
ERR_04139=Cannot validate {0} with a null SyntaxChecker
It would be really useful to test your code with the latest version so
that I can debug what's going on.
