I cannot help feeling like I want to steer away from
approaches like this because of the possibility that
these stateful beans will hang around for ever and
consume resources.
--- Chris Brown <[EMAIL PROTECTED]> wrote:
> Has anyone had success with or have suggestions on
> the following?
>
> Use a statefull session bean to handle queries from
> a client (servlet). The
> statefull session bean will create and hold on to
> the resultset on behalf of
> the client. The client controls the display of
> "result pages" to the user
> and calls methods on the statefull session bean to
> move through the
> resultset. The results are passed back to the
> client as a collection of
> "state" objects. The servlet will store a handle to
> the session bean in the
> session.
>
> Concerns:
> Is this the proper design?
> How long is the statefull session bean tied to the
> client?
> Passivate/Activate - will the resultset be
> serialized/deserialized properly?
> Can it handle large result sets? 20,000+ rows?
>
> Thanks in advance,
> Chris
>
>
===========================================================================
> 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".
>
=====
__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.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".
