Transfer does much more than just save and load objects. One of its most powerful features is the code generation it does, and one of the most powerful aspects of that is the management of composition.
Jaime -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Adam Haskell Sent: Wednesday, 23 April 2008 12:59 AM To: [email protected] Subject: [CFCDEV] Re: intialising cfcs > Coldspring is very handy to instantiate and wire your persistent service objects together on application start up. Right which is why I brought up ColdSpring, it didn't make sense to me to talk about composition of objects then talk about Transfer. Now admittedly I have not found a good reason to use Transfer so maybe I am missing something but I thought that was all about object persistence. Adam Haskell On Tue, Apr 22, 2008 at 10:15 AM, Nando <[EMAIL PROTECTED]> wrote: Transfer and ColdSpring - if it makes sense to use both. Transfer is going to be your main workhorse tho' in regards to your business objects. Coldspring is very handy to instantiate and wire your persistent service objects together on application start up. On Tue, Apr 22, 2008 at 4:01 PM, Adam Haskell <[EMAIL PROTECTED]> wrote: Transfer or ColdSpring? Adam H On Tue, Apr 22, 2008 at 9:58 AM, Nando <[EMAIL PROTECTED]> wrote: Sean Corfield has a presentation on Factories on his site in the right pod. Inheritance generally isn't needed when using ColdFusion, because type inheritance isn't needed, as it is in Java for instance. If you don't really know what you are doing yet with OO, I wouldn't bother with typing your CFC's at all. Use type=any or type=component. That gives you the flexibility to develop your model as you learn. I have a few blog posts on this at aria-media.com/blog if you haven't read them, in the "oo in cf" category. You also have to keep in mind that inheritance doesn't apply to instances of an object. You inherit (and can override) methods, but not data. Forgive me if I'm telling you something you already know. The implication here is that nothing special is needed when instantiating a component that inherits from another component, you just do it. CF takes care of making the methods available. If you need data available between objects, then you need to use composition instead of inheritance and you might as well make your life easy and use Transfer, because if you make your life difficult and try and work out how to do all this on your own, which a very good and very time consuming thing to do! you'll wind up using Transfer anyway one day. ;-) Hope that helps and I haven't misinterpreted your question too much. Nando On Tue, Apr 22, 2008 at 2:34 PM, Mark Ireland <[EMAIL PROTECTED]> wrote: Can anyone point me to a good tutorial on initialising cfcs of the basic kind? I mean teacher.cfc inherits staff.cfc inherits user.cfc and subject.cfc inherits course.cfc inherits student.cfc and so on Thanks ---------------------------------------------------------------------- at CarPoint.com.au It's simple! Sell your car for just $30 -- Nando M. Breiter The CarbonZero Project CP 234 6934 Bioggio Switzerland +41 76 303 4477 [EMAIL PROTECTED] -- Nando M. Breiter The CarbonZero Project CP 234 6934 Bioggio Switzerland +41 76 303 4477 [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
