Russ,
Hey there. Would you kindly clarify which question you are asking, exactly? DW On 9/21/07, Snake <[EMAIL PROTECTED]> wrote: > > Ok chaps, I am just reading the ColdSpring docs for the first time, and > going by the taxcalculator example I really can't see any advantage. > > If I have to implicity create a taxcalculator argument in my > ShoppingCartManager, then this is no less work than simply calling the > taxCalculator anyway. > As for having to pass init variables, well there is no reason to do that > within the ShoppingCart cfc anyway and I wouldn't do that, you would > initialise the taxCalculator elsewhere independantly of the cfc's that are > depndant on it, that is just common sense. > > I always put my CFC's in application scope anwyay so they only have to > instantiate once, and so all the cfc's can access each other anyway. > > And my config file would make sure they are all loaded in the correct > order > so that any dependencies do not fail, which to me is no different than > having to create the bean in the coldspring xml config file. > > In fact the ColdSpring method to me seems it has made the shoppingCart now > dependant on the taxCalculator cfc as you MUST pass it as an argument in > the > init method. So you would not even be able to initialise your shoppingcart > if there was any problem with the tax calculator. > > > -- > Russ > > > > > > > -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes
