Noted. Given that object instantiation via createObject is itself somewhat intensive, it makes sense to remove any layers or processes that aren't needed for my transients. I've found that Coldspring is very performant for my applications, so weight is very relative in this case. Thanks for the clarification.
anthony -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Tuesday, June 19, 2007 7:54 AM To: [email protected] Subject: [coldspring-dev] Injecting the Beanfactory into Service Objects On 6/19/07, Anthony Israel-Davis <[EMAIL PROTECTED]> wrote: > That makes sense. I didn't realize Coldspring was that heavy. Whilst I don't want to emphasize the "weight" of ColdSpring, I believe its object creation has three or four phases (dependency analysis, object creation and construction for all new dependent objects, setter injection). Something like that. It's been a while since I dug into the source code (I seem to recall a four phase process but can't remember details). -- 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
