Double-checking my understanding of DSRV-13 and DSRV-17 here: if I want to have Spring configure a module that doesn't currently do that, I need to:
o invent a unique module name ("MODULE"), such as "stats" for dspace-stats;
o implement SpringLoader somewhere in the module, returning a path to
${dspace.dir}/config/spring/MODULE/;
o add that implementation's fully-qualified class name to dspace.cfg as
springloader.modules.N;
o make sure that the configuration file winds up in
[DSpace-source]/dspace/target/dspace-VERSION-build/config/spring/MODULE.
Correct?
It looks like, right now, all of these config.s need to be in
[DSpace-source]/dspace/config/spring/MODULE to be assembled into the
aggregated target, yes?
I could not find any mention of Spring in the DSDOC configuration page.
--
Mark H. Wood, Lead System Programmer [email protected]
Asking whether markets are efficient is like asking whether people are smart.
pgpNDOh0ha7vM.pgp
Description: PGP signature
------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
