[midPoint] LDAP Resource configuration

[Radovan Semancik]

Hi,

You are trying to add resource object. MidPoint expects a file with a 
single top-level element <resource>. However you are most likely trying 
to add a file that contains multiple objects. Such files have top-level 
element <objects> and the individual objects are inside this element. 
Many sample resource files are structured like this. Mostly because they 
do not contain just a simple resource definition but also definition of 
synchronization tasks, object templates, etc. We have tried to make the 
samples somehow complete and stand-alone.

There is simple way to remedy your situation. Just use Configuration -> 
Import Object page. This page is more inteligent and can accepts files 
with multiple objects in them.

Hope this helps.

-- 

                                            Radovan Semancik
                                           Software Architect
                                              evolveum.com



On 10/02/2013 04:39 PM, Deepak Natarajan wrote:
> Hi Everyone -
>
> I am trying something very basic on my local Midpoint 2.2 instance - create a new LDAP resource configuration through the Administration GUI.
>
> I am running into this error :
> 	• Validation error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'resource'. One of '{"http://midpoint.evolveum.com/xml/ns/public/common/common-2a":object}' is expected.
> 	• Cause: cvc-complex-type.2.4.a: Invalid content was found starting with element 'resource'. One of '{"http://midpoint.evolveum.com/xml/ns/public/common/common-2a":object}' is expected. [ HIDE ERROR STACK ]
> org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'resource'. One of '{"http://midpoint.evolveum.com/xml/ns/public/common/common-2a":object}' is expected.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:417)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3182)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1806)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705)
> at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:273)
> at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:240)
> at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:186)
> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:104)
> at com.evolveum.midpoint.common.validator.Validator.validateSchema(Validator.java:446)
> at com.evolveum.midpoint.common.validator.Validator.validateObjectInternal(Validator.java:348)
> at com.evolveum.midpoint.common.validator.Validator.validateObject(Validator.java:336)
> at com.evolveum.midpoint.web.page.PageBase.validateObject(PageBase.java:490)
>
> I used the basic example from the samples - just modifying connector properties as needed :
>
> http://git.evolveum.com/view/midpoint/v2.2/samples/resources/opendj/   (opendj-localhost-basic.xml)
>
> Has anyone encountered this?
>
> Thank you.
>
> Rgds/Deepak
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint