Hi, As far as I remember it should also contain:
* Allow (pretty much any) string as OID. E.g. "whatever-oid" is often used instead of real OID by Sun/Oracle servers. And I have even see it recommended practice.
* Do not die when some of the schema parts is not there at all. E.g. Active Directory does not have SYNTAX definitions at all. It is OK to have these parts as null in the parsed schema, just the schema parser must not die on NPE or similar error during parsing.
Once you have the new parser working for your scenarios I can update my connector to a new Dir API version. And the I can run the tests with my private directory server ZOO.
-- Radovan Semancik Software Architect evolveum.com On 04/15/2018 11:03 PM, Emmanuel Lécharny wrote:
Hi guys, I'm trying to speedup the schema parsing (it's currently quite slow, due to the 3 embedded Antlr parsers we use). We use a quirksMode to be able to process more than just the RFC 4512 syntax. AFAICT, here are the relaxed rules : o Allow prefixed numericOID, like attributeType ( DUAConfSchemaOID:1.0 NAME 'defaultServerList' (assuming we have a DUAConfSchemaOID definedusing an objectidentifier definition) o Avoid checking references (SUP, SYNTAX) between schema elements o Allow the presence of special chars like '.', '_', ';', ':' and '#' in a NAME o Null OID are accepted for DitStructureRules Is there anything I'm missing ? Thanks !
