WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsCheers everyone for the hints - they directly led me to discovering
that both the local and extension jars were created but only the
domain jar was deployed to tomcat - and from there it was a shortish
step to a missing line in one of the build.xml's. At least the
documentation was spot on, even if the same cannot be said for my
editing skills. This is what I've been waiting for......
GET http://dev.collectionspace.smk.dk:8180/cspace-services/collectionobjets/e495042c-90ed-4ee3-8449
Response:
<document name="collectionobjects">
ns2:collectionobjects_smk</ns2:collectionobjects_smk>
ns2:collectionspace_core</ns2:collectionspace_core>
ns2:collectionobjects_common</ns2:collectionobjects_common>
ns2:collectionobjects_finearts</ns2:collectionobjects_finearts>
ns2:account_permission</ns2:account_permission>
</document>
/Chris
On 27 January 2012 02:01, Patrick Schmitz pschmitz@berkeley.edu wrote:
Note also that create_db on its own will not create the tables for your
extensions. They are created by the nuxeo logic when the web app
initializes. So, you have to fire up cspace and then when it is ready, take
a look at the DB.
Patrick
-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of
Christopher Pott
Sent: Thursday, January 26, 2012 11:02 AM
To: Aron Roberts; jmartinez@movingimage.us
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] problem adding extensions in version 2.0
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_nam
e}/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...
d+Schema+Extension
e+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
onspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.c
ollectionspace.org