Title: Message Title
|
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
4.1, 1.8.3, 3.2
|
|
Assignee:
|
Unassigned
|
|
Components:
|
DSpace API
|
|
Created:
|
02/May/14 1:36 PM
|
|
Environment:
|
Environment with the bundled handle server
|
|
Labels:
|
handle
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Jozef M.
|
|
Original Estimate:
|
0 minutes
|
|
Remaining Estimate:
|
0 minutes
|
|
Resolving a non existing handle returns an incorrect error code.
DSpace handle server returns
Error - Handle System Error
but it should return
Error - Not Found
(these particular errors are output by the local http proxy)
The culprit is ambiguous handle API documentation of previous versions. In the latest release the documentation says
... Return null to indicate handle not found; ...
The correct way is therefore to return null than throwing a
HandleException(HandleException.HANDLE_DOES_NOT_EXIST)
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
