I solved this, but thought I would say how in case anyone else had the same
problem.
First off, I worked out you can inspect what dspace is making of your
configuration by using the following command:
bin/dspace dsrun
org.dspace.discovery.configuration.DiscoveryConfigurationService <- incredibly
useful but so far as I can see undocumented feature.
>From there it became apparent that it was not reading the discovery.xml file
>in config/spring/api
When I was grinding my teeth on this problem I had renamed one of my files
An-old-discovery.xml and for some reason it was picking this one up.
Anyway renaming all the .xml files that were old versions to something like
.xml.old meant the correct file was picked up. bin/dspace index-discovery -b
and restart tomcat and it was working.
A little more digging and an-old.xml ban-old.xml and zan-old.xml and
zanoldandverylongfilename.xml all got picked up before discovery.xml, even if I
“touched” discovery.xml after creating the other files. So I have no idea why,
but don’t care. Undocumented feature - don’t have any valid discovery.xml files
ending with .xml in the config/spring/api directory!
Robin
> I have been updating discovery.xml, but for some reason recently when I
> update it, re-index (index-discovery -b) and restart tomcat, the changes are
> not reflected in the xmlui web app. Even a machine restart isn't helping.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
