Hello again,
thanx to Helix84 for the ideas. I really checked all the config-files, it's
definitely the same in test- and server-version (despite a difference due to
the other drirectory path...). I even tried setting all user all permission to
all dspace-realted folders. Nothing kept working. I even tried fresh installing
with anew build. The only thing left is to start with a new clean
vanilla-version and I really don't want to do that. Isn't there anybody who
might have an idea why dspace is unable to retrieve the Service for claimaction
or any other UserSelectionMethod ????
Maybe some of the XMLWorkflow-Developers?!?
Von: van Hoek, Wilko [mailto:wilko.vanh...@gesis.org]
Gesendet: Mittwoch, 2. Mai 2012 11:36
An: dspace-tech@lists.sourceforge.net
Betreff: [Dspace-tech] XMLWorkflow problem with claimaction
Hello everyone,
I'm having a some problem with my configurable workflow in dspace (1.8.3). I
configured it under my test-instance, which runs under windows 7, and ported it
to our server running Ubuntu. The workflow works perfect in the test-instance.
Testing it on the server I get a
org.dspace.xmlworkflow.WorkflowConfigurationException after the completeStep.
The Exception is thrown by the Step.java but resides to a fault in the
WorflowManager.java. I was able to narrow the problem down to the following
point.
The first Step in my workflow involves the userSelectionMethod claimaction. The
id can be extracted out of the workflow file but somehow the system is not able
to instantiate the UserSelectionActionConfig:
UserSelectionActionConfig userSelection =
createUserAssignmentActionConfig(userSelectionActionID);
After this line, userSelection is null and the setStep-Method in Step.java
throws the nullpointerException:
java.lang.NullPointerException at
org.dspace.xmlworkflow.state.Step.<init>(Step.java:51)
(line 51 in Step.java: userSelectionMethod.setStep(this);)
I tried changing the userSelectionMethod to claimAction, noUserSelectionAction
and autoassignAction, but I still ended up with the same behavior.
I have absolutely no idea why this is happening. I hope there is someone who
can help me with this.
Thanks in advance,
Wilko
workflow.xml:
<wf-config>
<workflow-map>
<name-map collection="default" workflow="default"/>
</workflow-map>
<workflow start="finaleditstep" id="default">
<roles>
<role id="editor" name="editors" scope="repository"
description="The people responsible for this step are able to edit the metadata
of incoming submissions, and then accept or reject them."/>
</roles>
<step id="finaleditstep" role="editor"
userSelectionMethod="claimaction">
<actions>
<action id="finaleditaction"/>
</actions>
</step>
</workflow>
</wf-config>
Stacktrace
----
Wilko van Hoek | A418 | tel. 526
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
