That makes sense. I didn't realize Coldspring was that heavy. I'll look into creating my own factory and injecting that. The objects I am currently working with are persisted externally and accessed via secure web services, so I haven't looked into Transfer, yet. That and I find I do better at addressing one thing at a time. I've got my head around Mach-II and finally (finally!) have a chance to dig into Coldspring. I suspect ORM will be next.
Thanks for the input, anthony -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Tuesday, June 19, 2007 7:22 AM To: [email protected] Subject: [coldspring-dev] Injecting the Beanfactory into Service Objects On 6/19/07, Anthony Israel-Davis <[EMAIL PROTECTED]> wrote: > Yes - I want to create transients in my service objects using the bean > factory, just as Peter suggests. Well, ColdSpring isn't designed for creating transients - it's designed to support resolution of dependencies, injection and AOP. Compared to simple createObject(), it's a fairly heavy process. I would recommend creating your own custom factory for your transients - and having ColdSpring create and inject the factory object. Personally, I have almost no transient objects that are unrelated to persistence in the database so I use Transfer ORM to manage nearly all my transient objects. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
