On 8/26/05, Brian Kotek <[EMAIL PROTECTED]> wrote: > A question here for the list. I'd like to know at what points you > decide to create a full business object vs. creating a Bean vs. > creating a transfer object. And don't just say "it depends"! Just > kidding...say it depends but try to explain what you think it depends > on. It depends on your definitions of "bean", "transfer object," and "business object." I think how you use them is inherent in the definitions.
If I have an object that represents an entity in a Domain Model, I probably won't really think of it as a "business object." I'd think of it as what it is -- a Product, a Customer, a ShippingAddress -- but if pressed, I'd probably categorize it as a "business object." If I want to get a bunch of related data from one part of the application to another, without passing each bit of data in a separate field, I might wrap the data up in a single variable. And I guess I'd have to label that variable a "transfer object." As for beans, well, it's easier for me to talk about a collection of beans. I tend to have several beans, mixed with rice, cliantro, a bit of cheese, maybe some chicken, wrapped in a totilla. Anyway, my point is I never find myself asking the question, "Is this a business object or a transfer object"? I arrive at the two from different directions. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.weblogs.us ---------------------------------------------------------- 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). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
