: > With all this talk about plugins, registries etc., /me can't help : > thinking that this would be a good time to introduce the Spring IoC : > container to manage this stuff.
I don't have a lot of familiarity with spring except for the XML configuration file used for telling the spring context what objects you want it to create on startup and what constructor args to pass then and what methods to call and so on -- with an easy ability to tell it to pass one object you had it construct as a param to another object you are hving it construct. on the whole, it seems really nice, and eventually using it to replace a lot of the home-growm configuration in SOlr would probably make a lot of sense ... but i don't think migrating to Spring is neccessary as part of the current push to support more configurable plugins for updates ... SOlr already has a pretty decent set of utilities for allowing class instances to be specified in the xml config file and have configuration arguments passed to them on initialization .. it's not as fancy as spring and it doesn't support as many features as spring, but it works well enough that it should be easy to use with the new plugins we start to add -- switching to spring right now would probably only complicate the issues, and probably wouldn't make adding Update plugins any easier. equally important: adding a few new types of plugins now probably won't make it any harder to switch to somehting like spring later ... which as i said, is something i definitely anticipate happening -Hoss
