Reiner Rosin wrote:
> If I got you right you've chosen to use EJB with no other reason than to
> find a solution for the scheduling problem. In my eyes this is the
> perfectly wrong way.
Er ... let me clarify. I've chosen to use EJB for all sorts of reasons.
We have a complex data model to represent our problem-domain, and a mess of
business-logic to manipulate it. We currently have a bunch of servlets that
implement business logic, presentation and data access (via JDBC). My plan is
to move the business logic into Session Beans, and most of the data-access into
Entity Beans, leaving the servlets to do presentation/control. I could perhaps
do this separation without EJB, but then I'd have to implement my own
transactional persistence layer.
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.
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.
--
Mike W
===========================================================================
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".
