> Sean Corfield: > You like making work for yourself, eh? :) Not really.. but I see your point ;)
> Jaime Metcher: > I don't want to trivialize it, but for me both ColdSpring > (the DI bit, not the AOP bit) and Transfer just immediately made sense. > Sean Corfield: > Transfer was much easier for me and I'm finding it > an incredibly productive way to build > out the data access layer of my applications now. Yes, I've read about both, but Transfer seemed to immediately "click" in a way that ColdSpring didn't. I understand they play different roles. And its nothing against ColdSpring. I just suspect its going to take a bit longer to get comfortable with. > Sean Corfield: >If you're using CFCs, use ColdSpring to manage your model. >If you're using CFCs, use cfcUnit to test your model. >If you're using CFCs, use Transfer or Reactor to persist your model. Thats a good way to sum it up. I'll check out cfcunit.org too. If anyone has any other good links on cfcUnit/dbUnit (articles, tutorials, whatever) feel free to post them. All in all very helpful information. Thanks guys. -- --------------------------------- Get your own web address. Have a HUGE year through Yahoo! Small Business. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
