Hi Clement,
Maybe the saslMutualAuthentication should be removed from 2?0 branch > XSD and only kept in trunk. Agree? > I suggest to keep the same XSD on the trunk and the 2.0 branch because it's already quite complex to manage. > > 3. I agree > > Ok, I will create an issue too. I will also patch the XSD. Does Java > code needs to be patched too? > You need to generate it through xjc tool: "$JAVA_HOME/bin/xjc" -d src/main/java -p org.lsc.configuration src/main/resources/schemas/lsc-core-2.0.xsd -b src/main/resources/schemas/lsc-core-2.0.xjc One day, I will remove the generated files from the LSC source code and use Maven to generate them at compilation time. > 4. Hooks: http://tools.lsc-project.org/issues/59 > > Ok, documentation will be updated on the wiki. > Thanks > > > 5. Plugins mechanism is provided to cover both license issues (i.e. NIS > jar) > > and to provide extensibility for closed source services. That's why NIS > > configuration is described in the standard XML even if it is a plugin. > > Extending XML is possible but quite time consuming so I'd like to avoid > > doing it if it is not strictly required. > > So maybe the XSD should be updated to have ExecutableLdifService defined? > Yes it should be done :) Kind regards, Sebastien.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
