Heh heh...not having to modify your "VO" doesn't buy you much when you have
to change your giant interface/class of String constants holding the keys to
your Map.
FWIW, I use Maps frequently to pass data values into my SQLMap statements
(the database I use is significantly different than my object data model)
and I'm grateful iBATIS supports them.
-Joe
----- Original Message -----
From: "netsql" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, March 14, 2006 3:58 PM
Subject: Re: How to make dao's / vo's more polymorphic
Using Collections for VO makes them *reusable*, which is what OO's only
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
view from version 1.0 of your web app to 2.0, and you can do so w/o any
code changes in the VO. Sorry that you do not see the benefits. I sure
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 talking
to back end.
.V
Clinton Begin wrote:
There's nothing OO
about them -- Period.
