Hi,
I’ve had a further dig into this and it seems that the db.name has
been removed on dspace v 5.x.x but is still referenced in the cris
version and so causes the problem. If I set the db.name = postgres in
the build.properties file it is not propagated to the dspace.cfg file.
If I set it directly in the dspace.cfg file then the exception goes
away and it has a further exception:
ERROR: column metadatavalue.item_id does not exist
this problems has been resolved with
https://github.com/Cineca/DSpace/commit/6578145e547db9f1468142e548ab1ce6c183102b
Please use the dspace-5_x_x-cris branch, we will make a fix release in
the next few days.
The class not found exception occurs in the sword, sword2, rdf, rest
and oai web applications if I remove these from the webapps directory
then the errors go away. The classes in the
dspace-api-CRIS-5.3.0.SNAPSHOT.jar files for these apps do not contain
the CrisSearchService class but they do contain the SearchService class.
Seems that there are a missing resources on classpath. You can found the
CrisSearchService.class into dspace-cris-api-CRIS-5.3.0.SNAPSHOT.jar but
perhaps the maven dependencies missed him.
Try to add the dependency to webapps pom files and rebuild the application.
e.g. dspace/modules/oai/pom.xml
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-cris-api</artifactId>
</dependency>
Thanks for your patience. Please keep us up-to-date with your progress,
we hope to achieve a better release together.
Best,
Andrea
Il 16/06/2015 15:20, alastair.dun...@stfc.ac.uk ha scritto:
I’ve had a further dig into this and it seems that the db.name has
been removed on dspace v 5.x.x but is still referenced in the cris
version and so causes the problem. If I set the db.name = postgres in
the build.properties file it is not propagated to the dspace.cfg file.
If I set it directly in the dspace.cfg file then the exception goes
away and it has a further exception:
ERROR: column metadatavalue.item_id does not exist
I’ve had a look in the database and it is correct it does not exist.
The class not found exception occurs in the sword, sword2, rdf, rest
and oai web applications if I remove these from the webapps directory
then the errors go away. The classes in the
dspace-api-CRIS-5.3.0.SNAPSHOT.jar files for these apps do not contain
the CrisSearchService class but they do contain the SearchService class.
I’ll move back to the 4.3.0 version for the present.
Alastair
*From:*alastair.dun...@stfc.ac.uk [mailto:alastair.dun...@stfc.ac.uk]
*Sent:* 02 June 2015 11:10
*To:* dspace-tech@lists.sourceforge.net
*Subject:* [Dspace-tech] Dspace-cris invalid db.name
Hi,
I’ve setup dspace-cris v 5.2.0 and this starts up and I can login ok.
I’ve added in the default CRIS objects and can browse to these ok.
This suggests that the db.name is valid. When I try and create a
researcher page and save this an Internal exception is thrown which
states that there is an invalid db.name:
java.lang.IllegalStateException: The configuration for db.name is
either invalid, or contains an unrecognised database
at
org.dspace.content.authority.AuthorityDAOFactory.getInstance(AuthorityDAOFactory.java:42)
at
org.dspace.app.webui.cris.controller.ResearcherPageDetailsController.handleDetails(ResearcherPageDetailsController.java:134)
at
it.cilea.osd.jdyna.web.controller.SimpleDynaController.handleRequestInternal(SimpleDynaController.java:116)
I don’t get this problem with v 4.3.0
Any ideas?
There are a few other problems when the system starts but these do not
seem to be a problem yet as I’ve not done any searching:
Failed to startup the DSpace Service Manager: failure starting up
spring service manager: Error creating bean with name
'org.dspace.servicemanager.spring.DSpaceBeanPostProcessor#0' defined
in class path resource [spring/spring-dspace-applicationContext.xml]:
Unsatisfied dependency expressed through constructor argument with
index 0 of type
[org.dspace.servicemanager.config.DSpaceConfigurationService]: :
Cannot find class [org.dspace.app.cris.discovery.CrisSearchService]
nested exception is java.lang.ClassNotFoundException:
org.dspace.app.cris.discovery.CrisSearchService
at
org.dspace.servicemanager.servlet.DSpaceKernelServletContextListener.contextInitialized(DSpaceKernelServletContextListener.java:92)
This is the final problem which eventually results in a null pointer
in the DspaceContextListener.
Exception sending context initialized event to listener instance of
class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'dspace.eventService' defined in
ServletContext resource [/WEB-INF/applicationContext.xml]:
Instantiation of bean failed; nested exception is
org.springframework.beans.factory.BeanDefinitionStoreException:
Factory method [public org.dspace.services.EventService
org.dspace.utils.DSpace.getEventService()] threw exception; nested
exception is java.lang.IllegalStateException: DSpace kernel cannot be null
Any help is appreciated.
Alastair
------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
