[Dspace-devel] [DuraSpace JIRA] (DS-1637) Support running handle server and application container on seperate machines

Thu, 22 Aug 2013 04:17:20 -0700

To be able to use org.dspace.handle.HandleManager.getHandlesForPrefix(Context, String) from XMLUI, I had to make it a public method. Serving information about handles and prefixes over XMLUI and JSPUI makes it accessible for anyone. But I don't see a problem with this, as these information were available over the handle server anyway.

I added a new pipeline to the sitemap.xmap and configured it to serve three pathes:
* <path-to-xmlui>/handleresolver/resolve/<handle> returns nothing (if handle does not exist) or the appropriate URL for the given handle.
* <path-to-xmlui>/handleresolver/listprefixes returns an array containing the prefix used by DSpace. I returned an array on purpose as the handle server can deal with multiple prefixes and perhaps there are reasons to use multiple prefixes in DSpace one day.
* <path-to-xmlui>/handleresolver/listhandles/<prefix> returns an array with all handles whose prefix begins with the given prefix. This is the same behavior as of HandleManager.getHandlesForPrefixe(Context, String).

All these information are returned as JSON.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira 
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to