have the bean submit a JMS request to a waiting thread, which
processes the request in parallel and sends a response. the requesting
bean then waits (with timeout!) on the JMS response. of course,
you have to use a server that has JMS support, like WebLogic.
--b
At 06:12 AM 5/20/99 , Grove, Andy wrote:
>When a client requests a set of schedules I call a fairly quick stored
>procedure to get a list of schedules that have been modified in the
>database, which returns zero rows most of the time but is still a bit slow.
>Ideally I would like to have this procedure running at the same time that I
>am loading objects from the disk based cache but the EJB spec prohibits me
>from spawning threads from within session beans.
===========================================================================
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".
