I'm going through ConfigurationManager and DSpaceConfigurationService looking for ways to harmonize their behavior -- see DS-1390 -- and I noticed DSpaceConfigurationService.getCatalina(). It seemed odd to tie DSpace to a particular servlet container, so I looked further.
It turns out that, if running under Tomcat, DSpaceConfigurationService
will try to find configuration in ${CATALINA_HOME}/dspace or
${CATALINA_BASE}/dspace. This is making assumptions, not only about
the choice of container, but about the structure of the container's
layout in storage.
I think this feature should go away. It assumes too much. I don't
recall seeing it documented anywhere. I wonder if anyone is using
this. (I can ask on dspace-tech, if you all agree this should be
removed.) We have plenty of other, more general ways to tell DSpace
where its configuration lies. I don't see that this one is all that
useful.
--
Mark H. Wood, Lead System Programmer [email protected]
Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
