-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I finally got it running ... But I'm not sure if the 'solution' shows up
an issue. I don't know if the order of given schemas to load matters. If
it shouldn't it's a problem. Maybe schemas are loaded line by line into
a e.g.Map and then processed. IIRC in this case we can garantee the
order an iterator fetches the elements.
Patch which solved the problem on my machine (note the "nis" schema
which is now loaded last). I didn't apply the patch, because if it's an
issue we should be reminded ...:
Index:
ldap-schema-manager-tests/src/test/java/org/apache/directory/shared/ldap/schema/loader/ldif/SchemaManagerLoadTest.java
===================================================================
- ---
ldap-schema-manager-tests/src/test/java/org/apache/directory/shared/ldap/schema/loader/ldif/SchemaManagerLoadTest.java
(revision 986263)
+++
ldap-schema-manager-tests/src/test/java/org/apache/directory/shared/ldap/schema/loader/ldif/SchemaManagerLoadTest.java
(working copy)
@@ -668,7 +668,7 @@
// Try to load a disabled schema when the registries does
// ot allow disabled schema to be loaded
- - assertFalse( schemaManager.load( "core", "nis", "cosine",
"InetOrgPerson" ) );
+ assertFalse( schemaManager.load( "core", "cosine",
"InetOrgPerson", "nis" ) );
assertFalse( schemaManager.getErrors().isEmpty() );
assertEquals( 38,
schemaManager.getAttributeTypeRegistry().size() );
Hope anybody has an idea about this.
Regards
Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxqfYIACgkQ2lZVCB08qHFSZACgz9x1ez/YVzB3VOP2ktPMbXFr
sAQAnRv1F0qjOUr6eU4zmZzNsVE170Ec
=Uf3N
-----END PGP SIGNATURE-----
