On Sun, 5 Mar 2000 17:31:48 -0800, Assaf Arkin <[EMAIL PROTECTED]> wrote:
>But that wasn't enough. We needed some way to schedule operations to
>occur at a given time, e.g. you can define that a certain process has to
>complete by a given date, or be cancelled if it's still in progress. You
>might want a transition to occur at the end of the day, etc.
>
>The solution for that was to add a scheduling ability which relies on
>JMS to deliver the messages, and entity beans to represent the scheduled
>activities so you can add/remove/query them.
>
>So far, works fine. But a scheduling engine must run as a separate
>continueous thread. That thread can be managed in one of two ways:
>
>1. It can be a connector plugged into the EJB server
>
>2. It can be a thread-bean
3. Use JMX and make a MBean. :-)
To me it sounds like the functionality you want is client-type functionality,
i.e. it will call other beans, but will never be called. Further,
one would want to manage it through some interface (start/stop/set interval).
>From your description this could easily be implemented as a JMX MBean. This
will require stepping outside the J2EE spec, but the functionality is still
provided through a standard specification (standard~=JCP spec.). It should be
very portable between different J2EE-servers supporting JMX.
I do not believe that your use-case warrants the introduction of, what you term,
a thread-bean. EJB is a component-model for server functionality, and as above,
your use-case sounds a lot like automated client-functionality.
Am I missing something?
/Rickard
ps. <vendor>The next version of EJBoss (www.ejboss.org) is being built entirely
on top of JMX.</vendor>
===========================================================================
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".
