As I said in my earlier post, I may not agree with it in principle,
but that doesn't mean ColdSpring shouldn't behave in the same fashion
as CF. Didn't mean to drag this through the mud again. ColdSpring now
does a very nice job of searching throughout the inherence tree for
all sorts of things like init methods, beanFactoryAware, etc.
And thanks for the patches Barney!
PS, how are you liking the Spring ST?? It's in the list I'm looking
at for a future upgrade...
Chris
Chris Scott
[EMAIL PROTECTED]
http://cdscott.blogspot.com/
http://www.coldspringframework.org/
On Jun 9, 2006, at 11:07 AM, Barney Boisvert wrote:
On 6/9/06, Tom Chiverton <[EMAIL PROTECTED]> wrote:
So you can't inherit constructors ? That makes more work doesn't it ?
I'm not aware of a language that has constructors and allows them to
be inherited, but CF doesn't have constructors, so it's a moot point.
With CS, init methods are no called if they're inherited. I've
supplied a patch (available attached to ticket 50) that will fix that,
though I'm not sure it works against the latest CVS versions any more.
It's actually more work to handle inheritance, because CS checks the
CFC metadata to see if an init method is present. Ignoring
inheritance requires a loop, while handling inheritance requires a
loop with a recursive ascension of the inheritance tree (because of
the way CF packages metadata.
The same inheritance-free design exists for the BeanFactoryAware
implementation, but my patch fixes this too. There is a valid set of
arguments both for and against supporting inherited init methods (I'm
on the 'for' side), but I think the setBeanFactory method (from
BeanFactoryAware) should definitely allow inheritance.
cheers,
barneyb
--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com/
Got Gmail? I have 100 invites.
