Wesley,
For problem 1, what are you seeing in your DSpace logs? In your
Catalina logs? Have you checked them for SQL or database errors?
Maury Bouchard
Simmons College GSLIS
Quoting Wesley Alan Wright wesley.wri...@uvm.edu:
I'm running a 1.6.2 Dspace server at
Are you using Postgres or Oracle? When I installed the REST API a
couple of weeks ago, I encountered the 500 internal server errors as
well. I solved them by placing the ojdbc14.jar in my CLASSPATH (I am
using Oracle). If you're using Postgres there may be an analogous
fix. Keep in
I solved this problem.
The REST API is using class oracle.jdbc.OracleDriver which is found in
the ojdbc14.jar This jar was not in my classpath. I copied it to
$JAVA_HOME/jre/lib/ext and after that, the API works. Everything is
obvious in retrospect but I am still confused as to why my
Greetings,
When I issue a collection level query such as:
http://192.168.56.111:8008/rest/collections/22.xml I get all items in
collection 22 (as expected) but the individual item level metadata
fields are empty, as in:
metadataentityid type=bean size=1
id type=number0/id
/metadataentityid
Hello,
I am attempting to use the REST API against a test repository. I am
using dspace 1.8.0 and Oracle express. My repository is working fine
(using the xmlui, I can add, change, and view communities,
collections, and items). I've checked out and built the REST API
after having changed
Thanks for the response, but I'm not sure what I'm looking in that
java file. In the startProviders method, I found the following code:
// for dev testing only COMMENT IN WORKING ENVIRONMENT
if (config.contains(dspace.dir)) {
config = /devel/dspace/config/dspace.cfg;
Greetings,
I've inherited a DSpace 1.6.1 repository and we're having problems
with the XMLUI. Specifically, variable *names* like
xmlui.ArtifactBrowser.FrontPageSearch.para1 for example are displaying
in the web browser instead of the *data* contained therein. Here's a
snippet of the
7 matches
Mail list logo
