|
Home > Archive > Apache Directory Project > November 2006 > [Mitosis] Integrating Quartz into ApacheDS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[Mitosis] Integrating Quartz into ApacheDS
|
|
| Alex Karasulu 2006-11-26, 1:11 pm |
| Hi Trustin + others,
Right now mitosis uses Quartz to manage triggering replication
schedules. We'll be adding much more replication related configuration
information for scheduled replication cycles in the near future.
Regardless quartz can be utilized by other parts of the system. For
example quartz can be used to trigger the execution of certain stored
procedures.
It would be nice to centralize the use of quartz so multiple services
can use this service.
I'm also thinking of adding some attribute types and objectClasses to
create special entries in the server for scheduled jobs/tasks.
Does this sound like it's something worth while?
Alex
| |
| Ersin Er 2006-11-26, 1:11 pm |
| On 11/26/06, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
> Hi Trustin + others,
>
> Right now mitosis uses Quartz to manage triggering replication
> schedules. We'll be adding much more replication related configuration
> information for scheduled replication cycles in the near future.
>
> Regardless quartz can be utilized by other parts of the system. For
> example quartz can be used to trigger the execution of certain stored
> procedures.
>
> It would be nice to centralize the use of quartz so multiple services
> can use this service.
>
> I'm also thinking of adding some attribute types and objectClasses to
> create special entries in the server for scheduled jobs/tasks.
>
> Does this sound like it's something worth while?
We can have a special container which has subordinate scheduling
entries. (Servers of the netscape family have such special funtional
containers.) As you said these entries can contain some special
attributes to specify scheduling time and tasks. This is somewhat like
UNIX cron registry. The missing thing is Jobs which can be implemented
as Stored Procedures (which are really code stored on DIT and can be
class-loaded easily).
> Alex
--
Ersin
| |
| John E. Conlon 2006-11-26, 1:11 pm |
| Spring offers integration hooks with Quartz and the TimerTask. Would
centralizing scheduling tasks via Spring be an alternative that could
help us to reduce or eliminate coupling with Quartz?
cheers,
John
On Sun, 2006-11-26 at 11:31 -0500, Alex Karasulu wrote:
> Hi Trustin + others,
>
> Right now mitosis uses Quartz to manage triggering replication
> schedules. We'll be adding much more replication related configuration
> information for scheduled replication cycles in the near future.
>
> Regardless quartz can be utilized by other parts of the system. For
> example quartz can be used to trigger the execution of certain stored
> procedures.
>
> It would be nice to centralize the use of quartz so multiple services
> can use this service.
>
> I'm also thinking of adding some attribute types and objectClasses to
> create special entries in the server for scheduled jobs/tasks.
>
> Does this sound like it's something worth while?
>
> Alex
>
| |
| Alex Karasulu 2006-11-27, 1:11 pm |
| John E. Conlon wrote:
> Spring offers integration hooks with Quartz and the TimerTask. Would
> centralizing scheduling tasks via Spring be an alternative that could
> help us to reduce or eliminate coupling with Quartz?
Hmmm I don't know if this alone will help us. The issue is that we have
to detect the addition of entries into the DIT and respond to those by
setting up certain jobs in Quartz.
According to this can this Spring integration help?
Alex
> On Sun, 2006-11-26 at 11:31 -0500, Alex Karasulu wrote:
>
>
| |
| John E. Conlon 2006-11-27, 7:11 pm |
| On Mon, 2006-11-27 at 11:02 -0500, Alex Karasulu wrote:
> John E. Conlon wrote:
>
> Hmmm I don't know if this alone will help us. The issue is that we have
> to detect the addition of entries into the DIT and respond to those by
> setting up certain jobs in Quartz.
>
> According to this can this Spring integration help?
Your right, in this case, trying to use only Spring may end up burdening
us with something more complicated than using straight Quartz.
cheers,
John
|
|
|
|
|