Got 'em and responded. I tried posting to this list at the same time I
posted to the dev list, but for some reason it didn't take until this
evening.
I thought I'd see if there are taglib users out there who would have a need
for this kind of thing.
Thanks again,
Bill Pfeiffer
----- Original Message -----
From: "Morgan Delagrange" <[EMAIL PROTECTED]>
To: "Taglibs-User" <[EMAIL PROTECTED]>
Sent: Wednesday, May 16, 2001 6:36 PM
Subject: Re: Proposal: DBTags and RowSet
> Hi Bill,
>
> I sent you a couple of emails on this topic.
>
> - Morgan
>
>
> On Wed, 16 May 2001, Bill Pfeiffer wrote:
>
> > Reposting my proposal for change to DBTAGS:
> >
> > BACKGROUND:
> >
> > For my current project, I have reworked the DBTags ResultSet tags (and
> > nested tags) to pull a javax.sql.RowSet out of a specified scope
attribute
> > and make the RowSet data available. This modification removes the
> > statement.execute() call and allows me populate the RowSet in another
tier
> > (EJB). My RowSet tag iterates just like the ResultSet tag and makes its
> > data available to nested tags in the same manner as ResultSet.
> >
> > After reviewing what I did, I thought it would make more sense for the
> > DBTags to support this, rather than do the rewrite that I did.
> >
> > PROPOSAL:
> >
> > I'd like to put forward the question to both the dev and user mailing
lists:
> >
> > Does it make sense / would it be useful for the DBTags to have the
option of
> > pulling a ResultSet object from some specified scope, as an alternative
to
> > performing a statment.execute() to obtain a ResultSet?
> >
> > Note that the object stored in the specified scope COULD be a RowSet as
> > RowSet implements ResultSet.
> >
> > BENEFIT(S):
> >
> > The major benefit of this approach would be the seperation of data
retrieval
> > (business logic) from data presentation.
> >
> >
> > What do you think?
> >
> > Bill Pfeiffer
> >
> >
> >
>
