Can start registered uno services on triggered events and handle there
own configuration and there lifetime. Such events are simple strings
wich meaning doesn't matter for any real service implementation of this
specification. But triggered events must be available inside the
configuration and some XJob s must be registered for that.
It's possible to start it synchronously ( XJob ) or asynchronously
( XAsyncJob ). But in general it's forbidden to use any UI inside
synchronous one. That can be the source of many trouble and will be forbidden.
A neccessary configuration of such job executor must support follow functionality:
- Same Job should be able to register for more then one event
- It must be possible to provide a place for job specific configuration data,
so the jobs doesn't be forced to use her own config implementation.
That's neccessary to perform whole operation because most possible events
can be occure during startup of an application. And configuration access
shouldn't make it slow. And one part of job interfaces is initialization
of it with her own config data.
- It must be possible to configure if a job wish to be started synchronous
or not.
Further it must be possible to deregister a successfully runned job.