> I'm still coming around... I need to fight the tendency to wrap too > much code, and functionality, in a single object.
There it is. The heart of the difficulty surrounding the OO paradigm shift. Identifying all the objects needed by a system is hard work. Implementing them is usually very simple. I absolutely love getting to the point in a project where coding actually starts, becuase it's like magic watching it all come alive. And if you did the design right, it comes together really fast. "pile of design docs" blink "functioning application". I LOVE that. cheers, barneyb On Wed, 17 Nov 2004 12:20:46 -0600, Dawson, Michael <[EMAIL PROTECTED]> wrote: > You know what... The more I re-read these past messages, I relized a > bean is closer, in concept, to a DTO than a BO. > > Several weeks ago Roland helped me on a VB project. He showed me the > notion of a user-related class which contained only properties, setters > and getters, but no logic other than what was needed to store and > retrieve the property values. > > Now that I see that the VB class was basically a bean, things are > starting to click. It is clear that passing a bean around to different > methods is much easier than passing all the argument as Barney mentioned > a few days ago. > > I'm still coming around... I need to fight the tendency to wrap too > much code, and functionality, in a single object. > > Fortunately, I should be attending an "Intro to Java OOP concepts for > Procedural Programmers" course soon. I hope to put more things together > by attending that course. > > Thanks > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/blog/ ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at [EMAIL PROTECTED]
