>Based on the feedback I've received, it seems that it might be most
appropriate
>to have a stand-alone Java thread that runs the scheduling engine.
That's actually the way we do it. It might be interesting however, keeping
resource management etc. in mind, to implement this type of behaviour using
a Thread pool, instead of just starting a high number of threads. It might
even be possible that your EJB container has a thread pool that you could
use through some provided API.
Hope this help,
Michael Moerman
THE CAPITAL MARKETS COMPANY
<mailto:[EMAIL PROTECTED]>
<http://www.capitalmarketscompany.com>
tel. + 32 495 58 88 46
fax + 32 3 821 14 12
*********************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
The Capital Markets Company.
http://www.capitalmarketscompany.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".
