Bill,
Could you submit your changes as a jar to the list.
I would be interested in looking at them.
Glenn
Bill Pfeiffer wrote:
>
> Glenn,
>
> The reworking I've done of the DBTags - ResultSet tag is using the Sun
> CachedRowSet. I happen to cast it to RowSet as defined by the j2ee api but
> the actual object creation on the ejb side is done using the early access
> CachedRowSet (1.0ea4) stuff.
>
> Bill Pfeiffer
>
> ----- Original Message -----
> From: "Glenn Nielsen" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 16, 2001 7:42 PM
> Subject: Re: Proposal: DBTags and RowSet
>
> > Morgan,
> >
> > Recently I have been looking at the CachedRowSet now available as
> > an early access download from Sun. The CachedRowSet combines the
> > connection, statement, and result set into one class. It can do
> > disconnected operations, so it works well in an environment where
> > you want to page through sub sets from the entire result set.
> >
> > Take a look at:
> >
> > http://www.javaworld.com/javaworld/jw-02-2001/jw-0202-cachedrow.html
> >
> > The question becomes, should DBTags support an API only available
> > as from Sun as an early access download. Perhaps call it experimental?
> > Do a conditional build of DbTags that includes support for CachedRowSet
> > if it exists at build time?
> >
> > Regards,
> >
> > Glenn
> >
> > Morgan Delagrange wrote:
> > >
> > > Hey Bill,
> > >
> > > I have to admit, I'm not too up on RowSets. I have a general idea what
> > > they're supposed to do, specifically in terms of portability around the
> > > environment, but I don't know them intimately. Do you have any ideas
> > > about how specifically you might alter the API? That might ground your
> > > ideas a bit for me.
> > >
> > > On Tue, 15 May 2001, Bill Pfeiffer wrote:
> > >
> > > > 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
> > > >
> > > >
> >
> > --
> > ----------------------------------------------------------------------
> > Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder |
> > MOREnet System Programming | * if iz ina coment. |
> > Missouri Research and Education Network | */ |
> > ----------------------------------------------------------------------
--
----------------------------------------------------------------------
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
