>> You don't have to change or maintain it.
That's an exaggeration. All software requires maintenance, perhaps Maps require less...but the end result is less as well.
A bicycle requires less maintenance than a sports car too....but I know what I'm driving home from work. ;-)
Cheers,
Clinton
On 7/3/05, netsql <[EMAIL PROTECTED]> wrote:
>
> 1) You don't have to write a JavaBean class.
>
>
;-)
2nd one:
2)You don't have to change or maintain it.
As project evolves and front end and back end evolve... there is no
maitanance or CRUFT or duplication.
I used to do beans for many years. Then I started w/ Groovy, CoR, C#,
Flash, etc... They all are Map and Collections based. Even when I make a
JTable it needs a collection. I my case, I have no needs for a bean. All
my API only takes Map args and sometimes return Lists. (A silly little
varargs). After all how often do you get a class cast exception!
.V
