title: Dropwizard filter priority - Customer Filter vs CORs filter
body: <p>I currently have two filters in my dropwizard app.
  One is CORs and the other filter is custom filter that checks header for any resource request to see if custom authorization token in the header is valid.  Individual filter works well without the other, but when I combine these two together always custom filter kicks in first.  I want CORs to be resolved before Custom filter kicks in.  Because when I call API from javascript, it requires CORs.  JSONP does bypass requirement of CORs, but it does not let you pass custom header over.  </p>
  
  <p>Oh I tried to use @Priority as well, but I can see how I can apply @Priority to my custom filter, but CORs is already defined and I am not sure how I can apply Priority.  </p>
  
  <p>If you need additional info, let me know.  </p>
  
  <p>Thanks.</p>