Laird Nelson wrote:
> Richard Monson-Haefel wrote:
> > I would argue that the ResultSet interface is far more reusable and usable then
> > an object graph or even an array of structures. The reason is simple, the
> > ResultSet interface never changes across queries. No matter what data is
> > captured the ResultSet interface remains the same. This makes it easier for
> > developers to work with because they already understand the semantics of the
> > interface (its always the same). In addition, it makes it easier for
> > requirements to change because it fairly simple to introduce new columns of data
> > or remove them.
>
> So the more flexible an object is the more reusable it is? But objects
> exist to place structure and order around an otherwise disorganized
> collection of data and behavior.
>
>
> Cheers,
> Laird
I'm pretty sure I never said that. My point was that the ResultSet interface is more
reusable in listing operations because its interface is designed for tabular data.. I
think this makes perfectly good sense if you think about it. Remember that we are
talking about listing behavior. Focus your thoughts on listing behavior and the
reusability of the ResultSet interface is obvious.
Richard
--
Richard Monson-Haefel
Author of Enterprise JavaBeans, 2nd Edition
Published by O'Reilly & Associates
http://www.EjbNow.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
