Thanks Ray, that did the trick. In case anyone else tries this, I also found it necessary to update the version numbers of the pom.xml's relating to my extensions (2.0-SNAPSHOT to 2.2-SNAPSHOT) as the build was failing with the original values. Cheers, Chris On 14 May 2012 18:40, Patrick Schmitz <pschmitz@berkeley.edu> wrote: > Ouch - that was a nasty documentation gap. We'll make a note to address > that. > > Thanks - Patrick > > ________________________________ > From: talk-bounces@lists.collectionspace.org > [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Ray Lee > Sent: Monday, May 14, 2012 8:22 AM > To: Christopher Pott > Cc: talk@lists.collectionspace.org > Subject: Re: [Talk] configuring extensions on v2.3 > > Hi Chris, > I had the same problem. It turns out there's been a change to the > tenant-bindings file. All of the xmlns uris have changed > from http://collectionspace.org/services/common/ to  http://collectionspace.org/services/config/. > I did a search and replace of those strings in tenant-bindings.delta.xml, > and it fixed the problem. > > Ray > > > > > > On May 14, 2012, at 6:03 AM, Christopher Pott wrote: > > Hi, > I’ve recently upgraded to v2.3 of Collectionspace, and merged my > configuration (domain and local extensions) from v2.0. Everything compiles, > and I can see that tables are generated for my extensions in the database. I > can create a collectionobject with no errors reported, both using the UI and > testing with directly to services using curl. However, any extension data I > provide is just ignored, and I can see it’s not being stored in the db. I’m > attempting some debugging, but can’t find the cause yet – Has anyone got any > advice on where I should concentrate my efforts? Any configuration > differences since 2.0 that I may have missed? > Regards, > Chris > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

Yes, that is a requirement. We have looked into making this more automatic, but the tools do not make it easy. Patrick > -----Original Message----- > From: talk-bounces@lists.collectionspace.org > [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of > Christopher Pott > Sent: Monday, May 14, 2012 11:09 AM > To: talk@lists.collectionspace.org > Subject: Re: [Talk] configuring extensions on v2.3 > > Thanks Ray, that did the trick. > > In case anyone else tries this, I also found it necessary to > update the version numbers of the pom.xml's relating to my > extensions (2.0-SNAPSHOT to 2.2-SNAPSHOT) as the build was > failing with the original values. > > Cheers, > Chris > > On 14 May 2012 18:40, Patrick Schmitz <pschmitz@berkeley.edu> wrote: > > Ouch - that was a nasty documentation gap. We'll make a note to > > address that. > > > > Thanks - Patrick > > > > ________________________________ > > From: talk-bounces@lists.collectionspace.org > > [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Ray Lee > > Sent: Monday, May 14, 2012 8:22 AM > > To: Christopher Pott > > Cc: talk@lists.collectionspace.org > > Subject: Re: [Talk] configuring extensions on v2.3 > > > > Hi Chris, > > I had the same problem. It turns out there's been a change to the > > tenant-bindings file. All of the xmlns uris have changed from  > > http://collectionspace.org/services/common/ to   http://collectionspace.org/services/config/. > > I did a search and replace of those strings in > > tenant-bindings.delta.xml, and it fixed the problem. > > > > Ray > > > > > > > > > > > > On May 14, 2012, at 6:03 AM, Christopher Pott wrote: > > > > Hi, > > I’ve recently upgraded to v2.3 of Collectionspace, and merged my > > configuration (domain and local extensions) from v2.0. Everything > > compiles, and I can see that tables are generated for my > extensions in > > the database. I can create a collectionobject with no > errors reported, > > both using the UI and testing with directly to services using curl. > > However, any extension data I provide is just ignored, and > I can see > > it’s not being stored in the db. I’m attempting some debugging, but > > can’t find the cause yet – Has anyone got any advice on > where I should > > concentrate my efforts? Any configuration differences since > 2.0 that I may have missed? > > Regards, > > Chris > > _______________________________________________ > > Talk mailing list > > Talk@lists.collectionspace.org > > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio > > nspace.org > > > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.c > ollectionspace.org >