Drew,
Well articulated.
[...]
My entire point here: it's all in the usage of the tool. I believe that Spring and Hibernate allow you to do things the right way. There will be a shakeout of best practices, but that's a very good thing for everyone. There will be "bad Spring" and "good Spring" and eventually all of the bad Spring will be filtered out as people learn and disseminate best practices.
I agree with this perspective.
To be able to make good decisions and to assess and determine "bad" vs "good" use of a technology / pattern / technique / idiom, one must fundamentally understand the goals being pursued. When I say things are reaching the "oops" stage of technology adoption, I mean that someone has gone too far down the long dark alley with their shiny new "hammer". I am simply suggesting that, at this point, one should back out of the alley, determine what they are trying to accomplish and reassess their choice of "hammers".
What I see in the article is an attempt to regain a sense of control in an IoC based system. The notion of separating the structural aspect of IoC wiring by placing structural interfaces as an inner element seems to be an attempt to reign in the "auto-wiring" capability. Maybe I'm missing the point, but it seems to me that this is an attempt to add complexity to solve the problem -- which to me is solving the problem the wrong way.
I await comments from those more expert in IoC.
Randy
-- Randolph S. Kahle, 6161 N Canon del Pajaro, Tucson, AZ 85750 Phone: +1 520 577 7680 [EMAIL PROTECTED] http://www.variantia.net Variantia
smime.p7s
Description: S/MIME cryptographic signature
