At 08:50 21.09.99 +0100, you wrote:
>Er ... let me clarify. I've chosen to use EJB for all sorts of reasons.
>
>So, while the change-scheduling requirement is an important part of the
>application, it's by no means the only part. I was just wondering if we could
>use EJBs to solve the scheduling problem.
I see. I missunderstood your posting in this point.
>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.
Another way might be to influence the right people to change the EJB specs.
I think there is a strong need to add the possibility to have own threads
within the EJB server. As long as these threads only use the standard EJB
interfaces to access EJB beans a container / EJB server should have no
problems to handle them correctly.
Regards Reiner
===========================================================================
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".
