fedora mountpoint property now appearing

Tue, Sep 25, 2007

The lack of any documentation on the CHH system other than a paragraph and a page of possible implementation scenarios has slowed me down a bit. I’ve managed to deduce that uploading a specially formatted XML file as a resource and setting its mountpoint property, in “Edit details” to the Fedora CHH impl:

mountpoint = uk.ac.uhi.it.ContentHostingHandlerImplFedora

should then cause the CHH system to delegate content handling to the Fedora implementation.

The problem was how to actually get that mountpoint property to appear. It doesn’t exist! sakai.UseCHH=true in sakai.properties doesn’t seem to do anything and the min-docs don’t mention anything about how to enable mount points. So it was on with the tweed cape and deerstalker, puff up the old pipe and get the magnifying glass out.

Turns out that what you see in “Edit details” is governed by:

content-tool/tool/src/webapp/vm/sakai_properties.vm and the line #if ($showMountPointProperty) got the old whiskers twitching. I followed the trail back to org.sakaiproject.content.tool.ResourcesAction, where the showMountPointProperty property is set depending on whether the ContentHostingService has Content Hosting Handlers enabled. It was then a simple trail to follow to org.sakaiproject.content.impl.DbContentService, where the CHH is injected by Spring.

The problem finally manifested itself. Inspecting components/sakai-content-pack/WEB-INF/components.xml showed that this line was commented out:

<property name=“contentHostingHandlerResolver”><ref bean=“org.sakaiproject.content.api.ContentHostingHandlerResolver”/></property>

uncommenting it and restarting solved the problem and I now have a mountpoint property appearing.

Elementary Dr. Watson I say!

comments powered by Disqus