On 5/10/06, Barney Boisvert <[EMAIL PROTECTED]> wrote:
My point is that the init method is NOT a constructor, and shouldn't be treated as such. In many cases, it behaves in a similar fashion, but it's really quite different. Out of that comes my opinion that ColdSpring should traverse up the metadata tree looking for an 'init' method in superclasses, along with the opinion that having a CFC with an inherited 'init' method is not only perfectly acceptable, it's good practice when possible.
This has been discussed at great length here over the last few months and we started in a situation where ColdSpring never traversed the inheritance tree for methods under any circumstances. We are currently in a situation where ColdSpring traverses the tree for some situations but not others. I actually drove the push to walk the tree in several of the cases where it does, now, do so. There was not sufficient consensus on the other situations to adopt a change from the status quo. Can you be a bit more specific about: a) which version of ColdSpring you are using b) how you are using it (which framework, autowiring, etc etc) c) why you have CFCs that don't have init() methods Just so we can understand your problem domain and mindset. -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
