Hi Mark,
There are 2 ways to ensure that a spring file is loaded, these are briefly
described below.
*As a Jar addon resource*
In the resources directory of a certain module a spring can be added if it
matches the following pattern: "spring/spring-dspace-addon-*-services.xml".
An example of this can be found in the dspace-discovery-solr block in the
DSpace trunk. (spring-dspace-addon-*discovery*-services.xml)
Wherever this jar is loaded (JSPUI module, XMLUI module, DSpace command
line, ...) the spring files will be processed into services.
*In the {dspace.dir}/config/spring directory*
This directory has the following subdirectories in which spring files can be
placed:
- *api*: when placed in this module the spring files will always be
processed into services (since the all the dspace modules are dependent on
the api)
- *discovery: *when placed in this module the spring will only be
processed when the discovery library is present (in the case of discovery in
the xmlui & in the command line interface).
- *jspui:* only processed for the jspui
- *xmlui:* only processed for the xmlui (example: the configurable
workflow).
The reason why there is a separate directory is that if a service cannot be
loaded, which would the case for the configurable workflow (the jspui would
not be able to retrieve the xmlui interface classes), the kernel will crash
and the UI will not started.
*General remarks*
A spring file can be located in a resource *and* in the config file, when
there are similar spring files the spring files in the configuration will
override these found in the resources (thus allowing users to configure
their own classes). It is indeed recommended to invent some kind of unique
name for your spring file as it is currently unknown to me what the effect
is of files with the same name.
If you have any further questions about the services feel free to email me.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 23 August 2011 22:08, Mark H. Wood <[email protected]> wrote:
> 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.
>
>
> ------------------------------------------------------------------------------
> 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
>
>
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
