Thanks Marcus, that was pretty straighforward. Instead of overriding
ApplicationServlet, I injected WebContext and got the Hivemind Registry
from there.
Since I'd like to start the scheduler on application startup, I also added
it to hivemind.EagerLoad. But, at that time the servlet hasn't been
initialized so there's no Hivemind Registry in the WebContext. Any
suggestions on how to work around this? Perhaps I can make the scheduler
start after the application has been initialized?
Martin
On Wed, 19 Jul 2006 08:41:25 +0200, Schulte Marcus <[EMAIL PROTECTED]>
wrote:
Using Quartz is not very difficult. I did it in the following steps
- write a HivemindServiceJobFactory which takes HiveMind-Services
implementing "Job" or "Runnable" and wrap them into an adapter taking
care
of calling setupThread and cleanupThread on the registry. The service-id
is
taken from the JobDetail's data-map unless there's only one Job
configured
as a hivemind service.
- write a ServiceImplementationFactory which retrieves the Scheduler from
the corresp. Quartz factory and replaces the Standard JobFactory with the
above one (attention: needs access to the registry - you'll need to
override
tap's application servlet to accomplish that)
marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
