I am a bit confused about the title of your post vs. the body of it...
If you are looking for a bean pooling strategy so that a multi-threaded
client (e.g.
servlet) can maintain a pool of sessions beans, and dole them out to threads
as
needed, I have a goodie I'd be willing to share that does this.
Send me a direct email if interested.
Regards,
-Chris.
> -----Original Message-----
> From: Stuart Thorn [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, May 11, 1999 4:10 AM
> To: [EMAIL PROTECTED]
> Subject: Client pooling
>
> I'm looking for a way of allowing one stateful session bean to call a
> function on all the other session beans rather like the
> javax.servlet.ServletContext.getServlets() method. How should one go about
> coding this sort of functionality in with EJB?
>
> ==========================================================================
> =
> 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".
