Skip to main content

Quartz.NET and MEF

I have been implementing a scheduler service for several different jobs on several difference schedules, which led me into using Quartz.NET. This is a really nice framework, but since we're using MEF I ran into some issues.

Quartz.NET basically consists of the scheduler engine which runs jobs implementing the IJob interface. The interface simply consists of an Execute method. I export each job with the IJob interface using MEF.

public class MyJob : IJob
    public void Execute(JobExecutionContext context)

In my scheduler implementation the jobs are imported into an IEnumerable<IJob>.

public IEnumerable<IJob> Jobs { get; set; }

The initialization of the scheduled tasks is pretty straight forward. A standard scheduler factory is initialized which in turn gives us a scheduler instance. Each job that was imported by MEF is then added to the scheduler, here with a simple 10 minute trigger just to make things easier.

var factory = new StdSchedulerFactory();
var scheduler = factory.GetScheduler();
foreach (var job in Jobs)
    var jobDetail = new JobDetail("Job name", job.GetType());
    var trigger = TriggerUtils.MakeMinutelyTrigger("Trigger name", 10, SimpleTrigger.RepeatIndefinitely);
    scheduler.ScheduleJob(jobDetail, trigger);

That is about everything we need to get the jobs going. The issue with MEF however is that each time a job is triggered to run the scheduler creates a new instance of the job. To prevent this behaviour we must create a custom implementation of the scheduler. The IJobFactory interface contains a NewJob method that is run each time a job is about to be run. We would like to return the same instance every time.

public class MefJobFactory : IJobFactory
    public IJob NewJob(TriggerFiredBundle bundle)
            var jobs = Bootstrapper.Instance.Container.GetExports<IJob>();
            return jobs.First(job => job.GetType() == bundle.JobDetail.JobType).Value;
        catch (Exception exception)
            throw new SchedulerException("Problem instantiating class " + bundle.JobDetail.JobType, exception);

There is one last thing to do to actually implement this custom job factory. Nothing in the code above needs to be changed. All we have to do is to add a few lines to the app.config to instruct Quartz.NET to use our custom implementation instead of the default.

        <section name="quartz" type="System.Configuration.NameValueSectionHandler, System, Version=1.0.5000.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
        <add key="quartz.scheduler.jobFactory.type" value="MyScheduler.MefJobFactory, MyScheduler" />

And thats it! Instead of creating a new instance of the job on each run, my custom implementation is used to get the MEF exported job.


Post a Comment

Popular posts from this blog

Binding a HTML-formatted string to a WPF WebBrowser control

Sometimes there is a need to display a HTML formatted string in a WPF application. There are a couple of ways to do this, but the most stright forward is to use a WebBrowser control and the NavigateToString method. This approach has one big flaw, you cannot use binding to a string out of the box, but I found a great solution through Stack Overflow which adds a bindable property to the  WebBrowser  control using  NavigateToString . The following class is all that is needed to add that behavior. A new depencency property named Html is introduced to the  WebBrowser  and the proper change action is performed in the OnHtmlChanged method. public class BrowserBehavior { public static readonly DependencyProperty HtmlProperty = DependencyProperty.RegisterAttached( "Html", typeof(string), typeof(BrowserBehavior), new FrameworkPropertyMetadata(OnHtmlChanged)); [AttachedPropertyBrowsableForType(typeof(WebBrowser))] public static string GetHtml(WebBrowser bro

Using Bootstrap Tooltip to show Parsley validation errors

I'm currently working on a web application using a variety of different frameworks, such as Backbone for the back-end, Bootstrap for the front-end and Parsley for client side form validation.  Parsley is a really powerful validation toolkit, but it takes some tweaking to make it blend with the Bootstrap front-end. Fortunately this is a one time fix, which can be re-used all over our project. Since there will be some custom options in our  Parsley  object, we can't use the default parsley-validate attribute on the form. Instead we have to initialize the validation with the jQuery syntax: $('#my-form').parsley(parsleyOptions); The options are were the magic happens, and in our case we have a global options object that our forms use to get the same experience all over the application. Here's what it looks like: var parsleyOptions = {  // Sets success and error class to Bootstrap class names  successClass: 'has-success',  errorClass: 'has-er

jQuery file upload with Bootstrap progress bar

Performing an asynchronous file upload from the browser is a common problem with almost as many solutions as there are developers. The following solution is the best fit for my needs, and also works well with most popular browsers. Backwards compatibility is not an issue in this case which is great, because I can use the new technologies as they are supposed to be used. Everything is put together in JSFiddle for a working example . I will continue to explain the parts below... First, the input field needs to be styled as a button. The form tag is only present for us to be able to reset the file input field later on. <form>     <span class="fileUpload btn btn-default">         <span class="glyphicon glyphicon-upload"></span> Upload file         <input type="file" id="uploadFile" />     </span> </form> .fileUpload { position: relative; overflow: hidden; } .fileUpload input { position: a