[midPoint] Re. How can we use a custom extension..?

[Deepak Natarajan]

Hi -

We have a custom LDAP object with a custom attribute :

APOSEmployee (super : inetOrgPerson)  with a custom attrib APOSUnit (DN String)

We have followed the midpoint "pirates" example (piracyPerson etc).

Unfortunately we are running into this error :

Get object (Model)
	• Schema error while processing schemaHandling section of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS)): Definition of attribute {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}APOSUnit not found in object class {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}AccountObjectClass as defined in account type definition 'default' in definition of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS))
	• Param: oid: 22ba8bc1-1712-4da6-a061-2dbe885c440e
	• Param: class: class com.evolveum.midpoint.xml.ns._public.common.common_2a.ResourceType
	• Param: options: [ObjectOperationOptions(ObjectSelector({.../common/common-2a}connector): GetOperationOptions(resolve=true, noFetch=null, raw=null, doNotDiscovery=null, retrieve=null))]
	• Get object (Provisioning)
		• Schema error while processing schemaHandling section of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS)): Definition of attribute {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}APOSUnit not found in object class {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}AccountObjectClass as defined in account type definition 'default' in definition of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS))
		• Param: oid: 22ba8bc1-1712-4da6-a061-2dbe885c440e
		• Param: type: class com.evolveum.midpoint.xml.ns._public.common.common_2a.ResourceType
		• Param: options: 
		• Context: implementationClass: class com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl
		• Complete resource (Provisioning)
			• Schema error while processing schemaHandling section of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS)): Definition of attribute {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}APOSUnit not found in object class {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}AccountObjectClass as defined in account type definition 'default' in definition of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS))
			• Cause: Definition of attribute {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}APOSUnit not found in object class {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}AccountObjectClass as defined in account type definition 'default' in definition of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS)) [ HIDE ERROR STACK ]
com.evolveum.midpoint.util.exception.SchemaException: Definition of attribute {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}APOSUnit not found in object class {http://midpoint.evolveum.com/xml/ns/public/resource/instance-2}AccountObjectClass as defined in account type definition 'default' in definition of resource:22ba8bc1-1712-4da6-a061-2dbe885c440e(APOS Engagement Resource (Apache DS))

We have also created a schema extension (like extension-piracy.xsd) and dropped this in our midpoint-home/schema directory. Any way we can check if this has been picked up? 

What are we missing...?

Many thanks!
-deepak