Issue #389 has been updated by Sébastien Bahloul. Category set to Core Status changed from New to Assigned Assigned to set to Sébastien Bahloul Target version set to 2.0.x branch
Hi Robin, You are completely right and I agree that ordering does not need to be checked. But at this time, I wasn't able to rewrite the XML Schema to allow unordered XML nodes to avoid a too hugly Java code generated by the JABX parser. If you have any idea, it will be welcomed to handle this issue ! Regards ---------------------------------------- Bug #389: XML Schema is overly strict http://tools.lsc-project.org/issues/389 Author: Robin Garner Status: Assigned Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 2.0.x branch Problem in version: 2.0rc1 The current XML schema requires many elements to appear in exactly the order they occur in the schema. For example in a <dataset> element, defaultValues, forceValues and createValues must appear in exactly that order. This makes it very difficult to write a config file without actually referring to the schema, and seems unnecessary. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
