Hi Chris, I noticed today that I couldn't get my schema extensions to get picked up in the app layer in version 1.12 and after a little comparison I noticed that the default domain files were missing a recent <root> tag that encompasses the entire file. The domain files in core have this and once I added this tag to my tenant domain files I could get my new fields to work as expected. I also believe this related to a new attribute in the base files' include tag: <include src="domain-collectionobject.xml" strip-root="yes"/>. Would it be wise just to remove this new attribute and leave the default domain schema files as is? - Jesse

the root tag is required else it wouldn't accept the inclusion of the service-record-paths at the right level in the document. And as they must be defined in the domain rather than base for extension schemas then root is the way forward. Which then must be removed in the include tag. It might seem redundant but it is required. Chris On 15/11/2011 00:14, Jesse Martinez wrote: > Hi Chris, > > I noticed today that I couldn't get my schema extensions to get picked > up in the app layer in version 1.12 and after a little comparison I > noticed that the default domain files were missing a recent <root> tag > that encompasses the entire file. The domain files in core have this > and once I added this tag to my tenant domain files I could get my new > fields to work as expected. I also believe this related to a new > attribute in the base files' include tag: <include > src="domain-collectionobject.xml" strip-root="yes"/>. Would it be > wise just to remove this new attribute and leave the default domain > schema files as is? > > - Jesse