WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsDear fellow implementers and developers,
I've just started working on CollectionSpace at SMK (with Chris Pott, he's on holidays for the moment).
We managed to create a tenant (smk) on my test-server, and it worked fine.
We managed then to configure a Local Schema Extension for this tenant, and it worked also well.
But after some changes in the code, this error message came up: Cannot set IS_REMOVED on removed or properties that are not map elements when trying to save a new record.
So, I went back to the first configuration (the Local Schema Extension we configured with Chris, the one that worked)... but still to find that error !
My understanding is, that there's something wrong between the fields defined in service (in my case collectionobjects_smk.xsd below)... :
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://collectionspace.org/collectionobject/local/smk"
xmlns="http://collectionspace.org/collectionobject/local/smk"
targetNamespace="http://collectionspace.org/collectionobject/local/smk" version="0.1">
<!-- Object identification information -->
<xs:element name="objectNumberSMK" type="xs:string"/>
</xs:schema>
...and the ones defined in application (domain-collectionobject.xml):
<root> <services-record-path id="smk">collectionobjects_smk:http://collectionspace.org/services/collectionobject/local/smk,collectionobjects_smk</services-record-path> <section id="domaindata">
<field id="objectNumberSMK" section="smk">
<selector>smk-collectionobject-objectnumber</selector>
</field>
</section>
</root>
But, as you can see above, there's not much to be confused about here: I added a simple field objectNumberSMK, where could be the error? (and moreover, as I said, it worked some days ago with the same files / fields).
And even stranger and confusing: when I look in cspace-services.log, just two lines above the Cannot set IS_REMOVED error, I find this line:
Invalid input document. No such property was found [dateLatestQualifier] in schema collectionobjects_common
No mention of my objectNumberSMK field, and I've never touched this dateLatestQualifier field???
Last precision: when I log in and save a record in the core tenant, it works just fine.
EDIT: last last precision: I've removed all the configuration for the Local Schema Extension. Error remains.
I hope that not all of you are sunbathing for the moment (or just in front of your computer screen), and that this problem sounds familiar to you.
Thanks by advance for your kindly help.
Cheers,
Sébastien
Sébastien Brossard
IT-Udvikler
sebastien.brossard@smk.dkmailto:3sebastien.brossard@smk.dkT
Tmailto:3sebastien.brossard@smk.dkT +45 3374 8483
Statens Museum for Kunst
Sølvgade 48-50
DK-1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dkhttp://smk.dk/
[Beskrivelse: Logo_mail]
Hi Sébastien,
I think you've done a really good job of isolating the problem. I'm
hoping that Michael Black's PAHMA deployment-related notes regarding this
issue may potentially prove helpful:
Best,
Aron Roberts
On Mon, Jul 16, 2012 at 7:29 AM, Sébastien Brossard <
Sebastien.Brossard@smk.dk> wrote:
Dear fellow implementers and developers,****
I’ve just started working on CollectionSpace at SMK (with Chris Pott, he’s
on holidays for the moment).****
We managed to create a tenant (smk) on my test-server, and it worked fine.
We managed then to configure a Local Schema Extension for this tenant, and
it worked also well.****
But after some changes in the code, this error message came up: Cannot
set IS_REMOVED on removed or properties that are not map elements when
trying to save a new record.****
So, I went back to the first configuration (the Local Schema Extension we
configured with Chris, the one that worked)... but still to find that error
!****
My understanding is, that there’s something wrong between the fields
defined in service (in my case collectionobjects_smk.xsd below)… :****
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://collectionspace.org/collectionobject/local/smk"*
xmlns="http://collectionspace.org/collectionobject/local/smk"*
targetNamespace="
http://collectionspace.org/collectionobject/local/smk" version="0.1">*
<xs:element name="objectNumberSMK" type="xs:string"/> *
</xs:schema>
…and the ones defined in application (domain-collectionobject.xml):****
<root>
<services-record-path id="smk">collectionobjects_smk:
http://collectionspace.org/services/collectionobject/local/smk,collectionobjects_smk</services-record-path>
<section id="domaindata">
*
<field id="objectNumberSMK" section="smk">*
<selector>smk-collectionobject-objectnumber</selector>*
</field>*
</section>*
</root>
But, as you can see above, there’s not much to be confused about here: I
added a simple field objectNumberSMK, where could be the error? (and
moreover, as I said, it worked some days ago with the same files / fields).
And even stranger and confusing: when I look in cspace-services.log,
just two lines above the *Cannot set IS_REMOVED error, I find this line:
Invalid input document. No such property was found [dateLatestQualifier]
in schema collectionobjects_common****
No mention of my objectNumberSMK field, and I’ve never touched this dateLatestQualifier
field???**
Last precision: when I log in and save a record in the core tenant, it
works just fine.****
EDIT: last last precision: I’ve removed all the configuration for the
Local Schema Extension. Error remains.****
I hope that not all of you are sunbathing for the moment (or just in front
of your computer screen), and that this problem sounds familiar to you.***
*
Thanks by advance for your kindly help.****
Cheers,****
Sébastien****
Sébastien Brossard**
IT-Udvikler**
sebastien.brossard@smk.dk 3sebastien.brossard@smk.dkT**
T 3sebastien.brossard@smk.dkT +45 3374 8483****
Statens Museum for Kunst****
Sølvgade 48-50****
DK—1307 København K****
T +45 3374 8494****
F +45 3374 8404****
smk.dk****
[image: Beskrivelse: Logo_mail]****
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
I had a similar example of this not too long ago. What worked in my case,
and may not for everyone(!), was to rebuild and deploy the entire service
layer rather than just the procedure I was working within. i.e. build from
services/ rather than from services/services/collectionobject
On Mon, Jul 16, 2012 at 11:42 AM, Aron Roberts
aron@socrates.berkeley.eduwrote:
Hi Sébastien,
I think you've done a really good job of isolating the problem. I'm
hoping that Michael Black's PAHMA deployment-related notes regarding this
issue may potentially prove helpful:
Best,
Aron Roberts
On Mon, Jul 16, 2012 at 7:29 AM, Sébastien Brossard <
Sebastien.Brossard@smk.dk> wrote:
Dear fellow implementers and developers,****
I’ve just started working on CollectionSpace at SMK (with Chris Pott,
he’s on holidays for the moment).****
We managed to create a tenant (smk) on my test-server, and it worked
fine. ****
We managed then to configure a Local Schema Extension for this tenant,
and it worked also well.****
But after some changes in the code, this error message came up: Cannot
set IS_REMOVED on removed or properties that are not map elements when
trying to save a new record.****
So, I went back to the first configuration (the Local Schema Extension we
configured with Chris, the one that worked)... but still to find that error
!****
My understanding is, that there’s something wrong between the fields
defined in service (in my case collectionobjects_smk.xsd below)… :****
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://collectionspace.org/collectionobject/local/smk"*
xmlns="http://collectionspace.org/collectionobject/local/smk"*
targetNamespace="
http://collectionspace.org/collectionobject/local/smk" version="0.1">*
<xs:element name="objectNumberSMK" type="xs:string"/> *
</xs:schema>
…and the ones defined in application (domain-collectionobject.xml):****
<root>
<services-record-path id="smk">collectionobjects_smk:
http://collectionspace.org/services/collectionobject/local/smk,collectionobjects_smk</services-record-path>
<section id="domaindata">
*
<field id="objectNumberSMK" section="smk">*
<selector>smk-collectionobject-objectnumber</selector>*
</field>*
</section>*
</root>
But, as you can see above, there’s not much to be confused about here: I
added a simple field objectNumberSMK, where could be the error? (and
moreover, as I said, it worked some days ago with the same files / fields).
And even stranger and confusing: when I look in cspace-services.log,
just two lines above the *Cannot set IS_REMOVED *error, I find this line:
Invalid input document. No such property was found [dateLatestQualifier]
in schema collectionobjects_common****
No mention of my objectNumberSMK field, and I’ve never touched this dateLatestQualifier
field???**
Last precision: when I log in and save a record in the core tenant, it
works just fine.****
EDIT: last last precision: I’ve removed all the configuration for the
Local Schema Extension. Error remains.****
I hope that not all of you are sunbathing for the moment (or just in
front of your computer screen), and that this problem sounds familiar to
you.****
Thanks by advance for your kindly help.****
Cheers,****
Sébastien****
Sébastien Brossard**
IT-Udvikler**
sebastien.brossard@smk.dk 3sebastien.brossard@smk.dkT**
T 3sebastien.brossard@smk.dkT +45 3374 8483****
Statens Museum for Kunst****
Sølvgade 48-50****
DK—1307 København K****
T +45 3374 8494****
F +45 3374 8404****
smk.dk****
[image: Beskrivelse: Logo_mail]****
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Aron, hi Jesse,
Thank you for your kindly help.
Unfortunately I had already tried your suggestions multiples times (I think I've entirely recompiled CS from scratch at least 20 times since last Friday). I was totally lost and couldn't understand at all - unless there was some kind of cache somewhere ?
So, before a last desperate try, I made a search on my server (with a scratch version, direct from git), a simple "find -name smk" command
How surprised I was when those emerged :
usr/local/share/tomcat/lib/tenant/smk
usr/local/share/tomcat/lib/cspace-config-smk.xml
usr/local/share/tomcat/nuxeo-server/shares/collectionobjects-smk.xsd
Once deleted, I could enjoy a fresh new installation without this @# IS_REMOVED error.
The moral of all this is: be careful folks, devil can hide in the depth of usr/local/share/tomcat !!!!
Thank you again for your help, have a nice day.
Cheers,
Sébastien
Fra: Jesse Martinez [mailto:jmartinez@movingimage.us]
Sendt: 16. juli 2012 17:47
Til: Aron Roberts
Cc: Sébastien Brossard; talk@lists.collectionspace.org
Emne: Re: [Talk] Cannot set IS_REMOVED when configuring a Local Schema Extension (under v2.3)
I had a similar example of this not too long ago. What worked in my case, and may not for everyone(!), was to rebuild and deploy the entire service layer rather than just the procedure I was working within. i.e. build from services/ rather than from services/services/collectionobject
I think you've done a really good job of isolating the problem. I'm hoping that Michael Black's PAHMA deployment-related notes regarding this issue may potentially prove helpful:
Best,
Aron Roberts
On Mon, Jul 16, 2012 at 7:29 AM, Sébastien Brossard <Sebastien.Brossard@smk.dkmailto:Sebastien.Brossard@smk.dk> wrote:
Dear fellow implementers and developers,
I've just started working on CollectionSpace at SMK (with Chris Pott, he's on holidays for the moment).
We managed to create a tenant (smk) on my test-server, and it worked fine.
We managed then to configure a Local Schema Extension for this tenant, and it worked also well.
But after some changes in the code, this error message came up: Cannot set IS_REMOVED on removed or properties that are not map elements when trying to save a new record.
So, I went back to the first configuration (the Local Schema Extension we configured with Chris, the one that worked)... but still to find that error !
My understanding is, that there's something wrong between the fields defined in service (in my case collectionobjects_smk.xsd below)... :
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://collectionspace.org/collectionobject/local/smk"
xmlns="http://collectionspace.org/collectionobject/local/smk"
targetNamespace="http://collectionspace.org/collectionobject/local/smk" version="0.1">
<!-- Object identification information -->
<xs:element name="objectNumberSMK" type="xs:string"/>
</xs:schema>
...and the ones defined in application (domain-collectionobject.xml):
<root> <services-record-path id="smk">collectionobjects_smk:http://collectionspace.org/services/collectionobject/local/smk,collectionobjects_smk</services-record-path> <section id="domaindata">
<field id="objectNumberSMK" section="smk">
<selector>smk-collectionobject-objectnumber</selector>
</field>
</section>
</root>
But, as you can see above, there's not much to be confused about here: I added a simple field objectNumberSMK, where could be the error? (and moreover, as I said, it worked some days ago with the same files / fields).
And even stranger and confusing: when I look in cspace-services.log, just two lines above the Cannot set IS_REMOVED error, I find this line:
Invalid input document. No such property was found [dateLatestQualifier] in schema collectionobjects_common
No mention of my objectNumberSMK field, and I've never touched this dateLatestQualifier field???
Last precision: when I log in and save a record in the core tenant, it works just fine.
EDIT: last last precision: I've removed all the configuration for the Local Schema Extension. Error remains.
I hope that not all of you are sunbathing for the moment (or just in front of your computer screen), and that this problem sounds familiar to you.
Thanks by advance for your kindly help.
Cheers,
Sébastien
Sébastien Brossard
IT-Udvikler
sebastien.brossard@smk.dkmailto:3sebastien.brossard@smk.dkT
Tmailto:3sebastien.brossard@smk.dkT +45 3374 8483tel:%2B45%203374%208483
Statens Museum for Kunst
Sølvgade 48-50
DK-1307 København K
T +45 3374 8494tel:%2B45%203374%208494
F +45 3374 8404tel:%2B45%203374%208404
smk.dkhttp://smk.dk/
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Terrific, Sébastien!
Thanks for sharing how you found this - still very much deployed -
extension schema, that appears to have been the cause of this issue!
On Tue, Jul 17, 2012 at 6:04 AM, Sébastien Brossard <
Sebastien.Brossard@smk.dk> wrote:
Hi Aron, hi Jesse,****
Thank you for your kindly help.****
Unfortunately I had already tried your suggestions multiples times (I
think I’ve entirely recompiled CS from scratch at least 20 times since last
Friday). I was totally lost and couldn’t understand at all - unless there
was some kind of cache somewhere ?****
So, before a last desperate try, I made a search on my server (with a
scratch version, direct from git), a simple “find –name smk” command
How surprised I was when those emerged :****
usr/local/share/tomcat/lib/tenant/smk
usr/local/share/tomcat/lib/cspace-config-smk.xml
usr/local/share/tomcat/nuxeo-server/shares/collectionobjects-smk.xsd
Once deleted, I could enjoy a fresh new installation without this @#
IS_REMOVED error.****
The moral of all this is: be careful folks, devil can hide in the depth of
usr/local/share/tomcat !!!! ****
Thank you again for your help, have a nice day.****
Cheers,****
Sébastien****
Fra: Jesse Martinez [mailto:jmartinez@movingimage.us]
Sendt: 16. juli 2012 17:47
Til: Aron Roberts
Cc: Sébastien Brossard; talk@lists.collectionspace.org
Emne: Re: [Talk] Cannot set IS_REMOVED when configuring a Local Schema
Extension (under v2.3)****
I had a similar example of this not too long ago. What worked in my case,
and may not for everyone(!), was to rebuild and deploy the entire service
layer rather than just the procedure I was working within. i.e. build from
services/ rather than from services/services/collectionobject****
On Mon, Jul 16, 2012 at 11:42 AM, Aron Roberts aron@socrates.berkeley.edu
wrote:****
Hi Sébastien,
I think you've done a really good job of isolating the problem. I'm
hoping that Michael Black's PAHMA deployment-related notes regarding this
issue may potentially prove helpful:
Best,
Aron Roberts****
On Mon, Jul 16, 2012 at 7:29 AM, Sébastien Brossard <
Sebastien.Brossard@smk.dk> wrote:****
Dear fellow implementers and developers,****
I’ve just started working on CollectionSpace at SMK (with Chris Pott, he’s
on holidays for the moment).****
We managed to create a tenant (smk) on my test-server, and it worked fine.
We managed then to configure a Local Schema Extension for this tenant, and
it worked also well.****
But after some changes in the code, this error message came up: Cannot
set IS_REMOVED on removed or properties that are not map elements when
trying to save a new record.****
So, I went back to the first configuration (the Local Schema Extension we
configured with Chris, the one that worked)... but still to find that error
!****
My understanding is, that there’s something wrong between the fields
defined in service (in my case collectionobjects_smk.xsd below)… :****
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"****
xmlns:ns="http://collectionspace.org/collectionobject/local/smk"*****
xmlns="http://collectionspace.org/collectionobject/local/smk"*****
targetNamespace="
http://collectionspace.org/collectionobject/local/smk" version="0.1">*****
</xs:schema>****
…and the ones defined in application (domain-collectionobject.xml):****
<root>****
<section id="domaindata">
*****
<field id="objectNumberSMK" section="smk">*****
<selector>smk-collectionobject-objectnumber</selector>*****
</field>*****
</section>*****
</root>****
But, as you can see above, there’s not much to be confused about here: I
added a simple field objectNumberSMK, where could be the error? (and
moreover, as I said, it worked some days ago with the same files / fields).
And even stranger and confusing: when I look in cspace-services.log,
just two lines above the *Cannot set IS_REMOVED error, I find this line:
Invalid input document. No such property was found [dateLatestQualifier]
in schema collectionobjects_common****
No mention of my objectNumberSMK field, and I’ve never touched this dateLatestQualifier
field???**
Last precision: when I log in and save a record in the core tenant, it
works just fine.****
EDIT: last last precision: I’ve removed all the configuration for the
Local Schema Extension. Error remains.****
I hope that not all of you are sunbathing for the moment (or just in front
of your computer screen), and that this problem sounds familiar to you.***
*
Thanks by advance for your kindly help.****
Cheers,****
Sébastien****
Sébastien Brossard****
IT-Udvikler****
sebastien.brossard@smk.dk 3sebastien.brossard@smk.dkT****
T 3sebastien.brossard@smk.dkT +45 3374 8483****
Statens Museum for Kunst****
Sølvgade 48-50****
DK—1307 København K****
T +45 3374 8494****
F +45 3374 8404****
smk.dk****
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
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org