One more small step to check on: verifying that the Nuxeo document type JAR file, containing your extension schema, has been deployed to the relevant folder within the Tomcat server folder, and whether that JAR contains your custom schema: You can check in $CSPACE_JEESERVER_HOME/nuxeo-server/plugins for this file. If it's present, you can also copy that JAR file into a new folder somewhere, expand it (e.g. jar -xf filename.jar), and look in the 'schemas' directory that will get created for your .xsd file for your extension schema. On Thu, Jan 26, 2012 at 11:01 AM, Christopher Pott <christopher.pott@gmail.com> wrote: > Hi, thanks for the pointers. The merged.xml file does contain > references to the new extensions. But more importantly, the extensions > are not to be found in the database. The create_db step at least > generates no errors so I'm still not sure why they are not being > created. > > /Chris > > On 26 January 2012 17:30, Aron Roberts <aron@socrates.berkeley.edu> wrote: >>  Completely concur with Jesse's suggestions. >> >>  The merged tenant bindings file - the one on the server, generated >> from your delta file, that matters for services schema extensions - >> can be found here: >> >>  $CSPACE_JEESERVER_HOME/cspace/config/services/tenants/{your_tenant_name}/tenant-bindings.merged.xml >> >> On Thu, Jan 26, 2012 at 7:22 AM, Jesse Martinez >> <jmartinez@movingimage.us> wrote: >>> Hi Chris, >>> >>> Here are some tips I would follow: >>> >>> Can you verify that the new extension fields exist in the postsql db? >>> >>> If they do, could you check to see if your tenant-binding.delta file >>> is correct and feeding into the .merged.xml file? >>> >>> Thanks, >>> >>>  - Jesse >>> >>> p.s. I've not built using a local and domain schema upon the same >>> tenant so my experience in that regard is limited. >>> >>> On Thu, Jan 26, 2012 at 9:18 AM, Christopher Pott >>> <Christopher.Pott@smk.dk> wrote: >>>> Hi, >>>> >>>> >>>> >>>> I’m trying to implement a shared domain schema extension (fine arts) plus a >>>> local schema extension (smk) on top of collectionobject, both to a newly >>>> created tenant (smk). The new tenant seems to work ok. I’ve followed the >>>> instructions at these resources, in this order… >>>> >>>> >>>> >>>> 1. http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant >>>> >>>> 2. >>>> http://wiki.collectionspace.org/display/DOC/How+to+Configure+a+Shared+Schema+Extension >>>> >>>> 3. >>>> http://wiki.collectionspace.org/display/DOC/How+to+Configure+Multiple+Local+or+Shared+Schema+Extensions+for+a+Tenant >>>> >>>> >>>> >>>> Building, deploying and installing according to the instructions above shows >>>> no errors, and new target files are generated. However, the two new schemas >>>> just don’t show up in the response when I use curl to GET a newly created >>>> collectionobject (even when created with data in one of the extensions). >>>> >>>> >>>> >>>> Does anyone have any advice on where should I look for errors? >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Chris >>>> >>>> >>>> >>>> IT Developer >>>> >>>> Statens Museum for Kunst >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org