There are other points that have been raised in this discussion that I'll
probably return to in the fullness of time, but I'll let it develop by
itself for the time being.
I do want to pick up one point you made though Mark.
On 4 June 2010 15:42, Mark H. Wood <[email protected]> wrote:
> At first I was concerned about the amount of wiring we'd need to knit
> together ~900 classes, and much of it repetitive. Every class that
> needs configuration, for example, would have to be injected with a
> reference.
This is something of a common misconception of Spring. In the documentation,
they generally refer to wiring 'components' - and I don't take that to mean
that there is / should be a 1:1 mapping between components and classes.
In other words, it would be reasonable to say that you have lower level
classes - that have dependencies passed in as references - which are
instantiated by higher level classes that are wired together by Spring,
being injected with references which they then pass on to the lower level
classes they directly instantiate.
Point being, that even in a monolithic environment, you have options other
than wiring everything together via xml or auto-wiring.
But in our case, were we are thinking about things in a modular way (with or
without osgi), then a module could / would have it's own Spring
configuration file. That configuration may not define resolutions for all
the dependencies itself - some may get bound by the osgi wiring if you
include a bundle definition (the bundle importing service definitions from
other bundles). Or those dependencies could be resolved by loading the
multiple configurations from many modules into one application-wide Spring
bean factory.
So, we may not necessarily be wiring through Spring all ~900 classes, and
even if we did, that wiring would be split into a number of logical module
boundaries, the wiring of each module (and the wiring across modules), being
individually manageable despite being an awful lot of wiring in total.
G
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
