directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSHARED-47) Testfailures on jdk1.5, jdk1.6 works in shared-ldap-schema-manager
Date Wed, 20 Jan 2010 17:30:54 GMT


Emmanuel Lecharny commented on DIRSHARED-47:

It seems we have *huge* bug in the way we manage SchemaObjects : we store those which are
standard Schema objects ( AT, OC, ...) in the global OidRegistry after having check that they
were not already present. Well, this is what we expect to do. The other schemaObjects are
not stored into the global OidRegistry (Normalizers, SyntaxChckers and Comparators).

Due to a wrongly '!' added in a if , the registries() method does the exact opposite.

Why does it works for java 1.6, and fail in java 5 ? It's funny : if you register first a
Normalizer with  an OID shared with some AT, then the global Oid Registry will contains the
OID, but as the AT's OID duplication is not tested due to the wrong check, it's ok. On the
other side, if you revert the registration, the duplication will be seen.

This is what happen : in java 6, we register first the normalizer, then the AT, and Java 5,
we register first the AT then the normalizer (it all depends on the order by which the associated
files are read from the disk).

Fixing and testing atm.

> Testfailures on jdk1.5, jdk1.6 works in shared-ldap-schema-manager
> ------------------------------------------------------------------
>                 Key: DIRSHARED-47
>                 URL:
>             Project: Directory Shared
>          Issue Type: Bug
>         Environment: linux
>            Reporter: Felix Knecht
>            Assignee: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 1.0.0-RC1
>         Attachments:,
> There are failing tests using jdk1.5 whereas the tests are passing fine when using jdk1.6
for the component shared-ldap-schema-manager

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message