title: How to define RequestMapping prioritization
body: <p>I have a situation where I need the following <code>RequestMapping</code>:</p>
  
  <pre><code>@RequestMapping(value={"/{section}"})
  ...method implementation here...
  
  @RequestMapping(value={"/support"})
  ...method implementation here...
  </code></pre>
  
  <p>There is an obvious conflict. My hope was that Spring would resolve this automatically and map <code>/support</code> to the second method, and everything else to the first, but it instead maps <code>/support</code> to the first method.</p>
  
  <p>How can I tell Spring to allow an explicit <code>RequestMapping</code> to override a <code>RequestMapping</code> with a <code>PathVariable</code> in the same place?</p>
  
  <p><strong>Edit 2:</strong> It seems that it would work if the <code>/support</code> mapping came before the <code>/{section}</code> mapping. Unfortunately we have dozens of controllers containing numerous methods with <code>RequestMapping</code>. How can I make sure that the controller with the <code>/{section}</code> mapping is initialized last? Or would a pre-interceptor be the way to go?</p>
  
  <p><strong>Edit 1:</strong> This is simplified, I know that having those two <code>RequestMapping</code> alone wouldn't make much sense)</p>