I'm currently preparing to create my first substantial OO/CFC based application, so you guys will probably be seeing a lot of questions from me in the near future :)
I was reading the list archives looking for form validation practices, and I found this thread (http://www.mail-archive.com/[email protected]/msg09518.html). In the thread a number of people mention "beans", and that they often allow any string value to be used in the bean's mutator methods, but they reference a validator method before doing anything with the bean. What exactly is a "bean" in regards to CFCs? My (very limited) understanding of JavaBeans is that they are simple classes that conform to special naming conventions, and these conventions make it possible to plug those beans into editors that know how to reference the beans. So in "CFC land" is a bean just a simple object with getter/setter methods, but no business logic? If this is true, how are they different from lightweight transfer objects? In what situations do you use beans, and when do you use heavyweight objects? Thanks in advance, Seth ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
