Disconnected RowSets and CachedRowSets sounds a lot like MS ADO Disconnected
recordsets. MS uses these with MTS components which in turn reminds EJB
stateless session beans. I guess this works despite MS ;-)
RowSets are by default closely connected to the database. One question is
how you populate the RowSet if you want to use more OO aproach (i.e. build
the RowSet content out of objects or components). RowSets and stateless
session beans might also be an alternative to the "read-only queries" or to
some other, straightforward database access need.
Regards,
Jouni
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Saturday, March 04, 2000 11:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Patterns for massive amounts of data?
>
>
> (I sent a reply to this post earlier, but it seems to have been
> discarded by the mailserver... typical..)
>
> > IF you use a session bean, it must load all the records, serialize them
> > and return a serialized copy. So you get the overhead of serialization
> > (which is pretty significant) and you don't benefit from the value of
> > fetch buffers (which gives bettern response time).
>
> This is not necessarily correct. A bean could return a RowSet. There's a
> tutorial on this on the JDBC homepage. The RowSet could either be
> pre-fetched, or it could do fetching as needed. This would allow you to
> use only EJB's to interface with your model, instead of doing
> servlet-JDBC workarounds.
>
> Far-out idea:
> Shouldn't it be possible to have methods in EntityBean home interfaces
> that looks something like this:
> RowSet getDisplayData()
> * When called it could get data for that particular EntityBean,
> according to some declarative info about what attributes and what "rows"
> should be returned.
> * Since this is in the EntityBean interface the container can make sure
> that the data is correct, either by first synching all cached instances
> with DB, or by synching the data from the db with the data in the live
> entity instances (either will give proper results).
> * This will be a solution for having some interaction through
> entitybeans and some through JDBC accesses. Now all calls to the
> "logical" entity goes through the entitybean interface.
>
> Am I missing something or could this really work?
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.dreambean.com
> Question reality
>
> ==================================================================
> =========
> 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".
>
===========================================================================
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".
