Aaron, What really is a service layer compared to your implementation of ORM objects? In essence, it is an abstractor that creates shorter foot prints on calling functionality.
The one to many relationship in Reactor creates an instance of the child object into the parent relationship. Reactor has configurations in the reactor.xml to define object relationships. The one to many takes the "one" parent relationship and places an object call to the "many" object. So, you could create a DAO for the parent realtionship and an iterator for the child relationship inside of a service that would combine the two together. Frameworks like Model-Glue just register the factory as a service and you can reference the ORM anywhere in your MVC controller. Teddy On 12/7/06, Aaron Roberson <[EMAIL PROTECTED]> wrote: > > Teddy, > > I have checked into both Reactor for ColdFusion and Transfer ORM. What > I don't like about Reactor is the ActiveRecords implementation - not > because there is anything wrong with it but that I am still learning > and don't know much about it. > > Transfer seems much more "up my alley", but at present I am wanting > full control over my code as I am building my first OO application. > The code generation and automatic updating is really neat, and I will > probably rely on it heavily in the future. However, at this time I > really need to get in and learn what the code is doing and prefer to > update my objects when the database changes, etc. > > As far as "comparing notes", I believe that one-to-many relationships > have to be hand coded as custom gateways. However, I do recall that > you can specify relationships in the config.xml file and it will > generate the code from there. The only problem is that both transfer > and reactor do not use service layers, which changes things a bit. > > -Aaron > > On 12/7/06, Teddy Payne <[EMAIL PROTECTED]> wrote: > > Have you thought of exploring Reactor for ColdFusion( > > http://trac.reactorframework.com/reactor)? It is an ORM that implements > > this idea. You can compare notes so to speak. > > > > Another interesting ORM is Transfer ( > > http://www.compoundtheory.com/?action=transfer.index). > > > > Teddy > > > > > > On 12/7/06, Aaron Roberson <[EMAIL PROTECTED]> wrote: > > > > > > I have an OO newbie question about ORM and composition. > > > > > > Is it better to create a "has-a" relationship between one-to-many > > > objects than to just invoke the objects separately? > > > > > > For instance, I have a product object (bean, DAO, gateway and service) > > > and a product items object (bean, DAO, gateway, service). Each product > > > has many product items. Is it better to map the product items to the > > > product object (array, struct or query) through the product's service > > > layer or to just invoke each object and pass them the product id? > > > > > > I hope my question is clear. Thanks for your help, > > > 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:263226 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
