Cascading initialization

[Rod Widdowson]

You will have spotted that I have moved to the custom-schema equivalent of
'default-init="initialize"' in the attribute filter and attribute resolver.

This wasn't exactly a slam dunk since if the initialization method doesn't
exist then spring will fail to create the beans.

The next stage I'd like to look to is to remove the explicit initialization
cascading  that the attribute filter and attribute resolvers do - Spring is
(or should) be calling initialize for us, so do we need to do it again?
(I’ll not that #initialize() can be called multiple times.

Does anybody think that this is a *bad* idea?

Rod