point taken... one of the things I realized while reading about patterns, is that I was already using some of those patterns without knowing; I just arranged my objects in such a way that made sense... some time later, I found out that someone had given an "official" name to that pattern... while today it may be important to know the exact pattern name so that all of us know what the other is talking about, even more important is the fact that we use patterns to make our lives easier..
Do not take this as a rebuttal... rather as an encouragement for people to use/think in patterns and architecture instead of seat-of-the-pants, hack-away solutions. As for me, I'll continue using these patterns and I'll look at martinfowler so that I can learn the correct definition of these two patterns. Thanks for your clarifications. Axel Guerrero -----Original Message----- From: Hal Arnold [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 1:50 PM To: OJB Users List Subject: RE: Changing object properties outside the transaction ... Not to be a prig, but the term "value object" has a specific meaning and is not the same as a data transfer object. This confusion has been amended in the J2EE patterns book (Alur/Malks/Crupi) in the second edition because of all the confusion it caused. see: http://martinfowler.com/eaaCatalog/valueObject.html -----Original Message----- From: Philippe Hacquin [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2003 2:26 PM To: OJB Users List Subject: Re: Changing object properties outside the transaction ... Hi, using such "view objects" is a common J2EE pattern (the value object, or data transfer object). I use it extensively in Struts and OJB applications. It <snip> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
