Hi James,

I'm glad that you succeed to fix the issue on your own. You are completely
right, the order doesn't matter at all, but our parser and the piece of
code which is based on XSD (XML Schema) and JAXB does not seem to be able
to consider the different elements without order. If you find some helpful
links, I'd be happy to remove such constraint !

Best regards,
-- 
Sebastien BAHLOUL
IAM / Security specialist
Ldap Synchronization Connector : http://lsc-project.org
Blog : http://sbahloul.wordpress.com/



2012/4/12 James McCartney <[email protected]>

> Sorry to answer my own question.  :)
>
> I made this work by moving the conditions stanza down in the file.  I did
> not think that order mattered among XML element siblings, but in this case
> it does.
>
> ...
>
> <defaultDelimiter>;</**defaultDelimiter>
> <defaultPolicy>FORCE</**defaultPolicy>
> <conditions>
> <create>false</create>
> <update>true</update>
> <delete>false</delete>
> <changeId>false</changeId>
> </conditions>
> <dataset>
> ...
>
> I just found this article which seems to allow for ordering of sibling
> elements in XML:
>
> http://www.ibm.com/**developerworks/xml/library/x-**eleord/index.html<http://www.ibm.com/developerworks/xml/library/x-eleord/index.html>
>
>
> On 04/12/2012 12:08 PM, James R. McCartney wrote:
>
>> I am working with the lsc 2.0rc2 sample for hsqldb and the delivered
>> sample works great!  I want to _update_ entries only, not create,
>> delete, or change the ID on entries.  I believe that I need to add a
>> conditions but am having trouble.
>>
>> I changed the sample lsc.xml to include the conditions that I need and
>> left the rest to default.  I get an error:
>>
>> ...
>> <propertiesBasedSyncOptions>
>> <conditions>
>> <create>false</create>
>> <update>true</update>
>> <delete>false</delete>
>> <changeId>false</changeId>
>> </conditions>
>> <mainIdentifier>"mail=" + srcBean.**getDatasetFirstValueById("**mail") +
>> ",ou=Sample,dc=lsc-project,dc=**org"</mainIdentifier>
>> <defaultDelimiter>;</**defaultDelimiter>
>> <defaultPolicy>FORCE</**defaultPolicy>
>> ...
>>
>> [org.xml.sax.**SAXParseException; systemId:
>> file:/home/james/Documents/**directory/lsc_sync/lsc-2.0rc2/**
>> sample/hsqldb/bin/../etc/lsc.**xml;
>> lineNumber: 56; columnNumber: 15; cvc-complex-type.2.4.a: Invalid
>> content was found starting with element 'conditions'. One of
>> '{"http://lsc-project.org/XSD/**lsc-core-2.0.xsd<http://lsc-project.org/XSD/lsc-core-2.0.xsd>
>> ":**mainIdentifier}' is
>> expected.]
>>      at
>> org.lsc.configuration.**JaxbXmlConfigurationHelper.**getConfiguration(**
>> JaxbXmlConfigurationHelper.**java:153)
>> ~[lsc-core-2.0rc2.jar:na]
>> ...
>>
>> Does anyone know how to change the hsqldb sample to only update LDAP
>> attributes, not add or delete entries?
>>
>>
> --
>
> James McCartney
> System Administrator
> IT Services, University of Arkansas
>
>
>
> ______________________________**______________________________**___
> Ldap Synchronization Connector (LSC) - http://lsc-project.org
>
> lsc-users mailing list
> [email protected].**org <[email protected]>
> http://lists.lsc-project.org/**listinfo/lsc-users<http://lists.lsc-project.org/listinfo/lsc-users>
>
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users

Reply via email to