Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE:  Re: How to make dao's / vo's more polymorphic
Date: Tue, 14 Mar 2006 17:11:26 -0500
Message-ID: 
 <F9994DF29A98C848AFA24E939471E5B601F653A8@pepwmu00195.corp.pep.pvt>
Thread-Topic: Re: How to make dao's / vo's more polymorphic
Thread-Index: AcZHrDxo58N/+tpjTAemHoIqD/J2CQAB0pcQ
From: "Voorhoeve, Niels {PBG}" <niels.voorhoeve@pepsi.com>
To: <user-java@ibatis.apache.org>

I beg to differ.  I think one of the primary goals of OO is to make the
semantics of the object transparent, hence comprehensible, hence
reusable.  Your approach completely negates that goal and in fact
obfuscates the code (unless you are the privileged programmer who wrote
it in the first place and has the whole mess memorized). =20

-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of netsql
Sent: Tuesday, March 14, 2006 3:58 PM
To: user-java@ibatis.apache.org
Subject: Re: How to make dao's / vo's more polymorphic

Using Collections for VO makes them *reusable*, which is what OO's only=20
goal, to make you more productive via reuse.
They are dynamic VO in the sense that one cad add a column in SQL or in=20
view from version 1.0 of your web app to 2.0, and you can do so w/o any=20
code changes in the VO. Sorry that you do not see the benefits. I sure=20
used to do the "beans" way for many years, but now I gave it up.

Plenty of people do it that way. I "learned" it from ActionScript=20
talking to back end.

.V

Clinton Begin wrote:
   There's nothing OO
> about them -- Period.
>