Ganesh,
If your bean always uses the same other beans to do its work, there is no
reason not to hoold onto a reference. Understand that your are not really
hold a reference to a bean but rather a reference that the EJB
server/container has serverd up. You only clog up the works if you hold onto
other stateful beans.
I recall some previous posts on stateful beans holding on to stateful
beans... As I recall this was generally poopoo'd by the list.
Regards,
-Chris.
> -----Original Message-----
> From: Ganesh Venkataraman [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, July 20, 2000 1:17 PM
> To: [EMAIL PROTECTED]
> Subject: Stateful Session bean
>
> Is it a good practise to have Remote Objects defined as Persistent
> variables
> in a Stateful Session Bean.
>
> Should I use a stateful session bean only to hold values from a HTML page
> or
> can I also use it save Remote Objects.
>
> Thanks and regards
> Ganesh
>
> ==========================================================================
> =
> 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".
