To Spring or not to Spring? (was: Update Plugins)
On 1/16/07, Alan Burlison [EMAIL PROTECTED] wrote: Bertrand Delacretaz wrote: .../me can't help thinking that this would be a good time to introduce the Spring IoC container to manage this stuff... Please, no. I work on a big webapp that uses spring - it's a complete nightmare to figure out what's going on. Using just the IoC container? I'm not talking about full-blown Spring magic, *just* IoC to assemble plugins. Spring's IoC is not complicated, and logging statements and debuggers are here to find out exactly what's happening if needed. I don't think it'd be more complicated than using our homegrown plugin system. Only more tested, documented and well-known. -Bertrand
Re: To Spring or not to Spring? (was: Update Plugins)
Bertrand Delacretaz wrote: Using just the IoC container? I'm not talking about full-blown Spring magic, *just* IoC to assemble plugins. Spring's IoC is not complicated, and logging statements and debuggers are here to find out exactly what's happening if needed. I don't think it'd be more complicated than using our homegrown plugin system. Only more tested, documented and well-known. It just seems like a big hammer to crack a small nut. I've had *bad* experiences with apps where people pulled in just about every framework, component and widget you can think of - to understand what the hell is going on you end up having to be an expert in all of them. Yes, I'm probably just paranoid ;-) -- Alan Burlison --
Re: To Spring or not to Spring? (was: Update Plugins)
On 1/16/07, Alan Burlison [EMAIL PROTECTED] wrote: ...I've had *bad* experiences with apps where people pulled in just about every framework, component and widget you can think of... That's what you previous message seemed to imply ;-) I agree that, if we start using Spring (or another) IoC container, we must be careful to use what actually helps us, and not let it become our Code Dictator... -Bertrand
