Another reason why I did not use an object factory is because I noted the fact that you have to register all the DAO's, gateways and beans with the full path in Application.cfm. It seemed just as easy to instantiate all of my objects directly in Application.cfm and assign them to the application scope. With my current method I am still only setting the path in one place. I can also reference all of my objects from any part of the application that is in the same directory as Application.cfm without having to know how it is instantiated.
However, I think that Phill's ObjectFactory.cfc does not instantiate the objects when registered in Application.cfm. Instead, I believe that all of the details are placed in a struct that can be be referenced at any time. The advantage of this would be that the objects are not instantiated until they are actually used. You still get the benefit of having only one copy of the object in memory and you do not have to use a full path to the object when instantiating it in the view or controller. If that is the case, I just talked myself into using Phill's ObjectFactory.cfc. The benefit over my current method would be that the objects are not instantiated until they are used. Even if a request to instantiate the object is made several times across several pages, there is still only one copy of the object in memory because complex objects are passed by reference. -Aaron ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:263605 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
