title: Swagger (spray) path parameters inside resource url
body: <p>Say I have a parametrized resource url like</p>
  
  <pre><code>/customers/{CUSTOMER-ID}/ownedItems/{ITEM-ID}
  </code></pre>
  
  <p>How should I annotatate/split my spray routes (using the spray-swagger plugin) to generate a documentation that will recognize {CUSTOMER-ID} as a proper path parameter?</p>
  
  <p>My problem is that the top level @Api annotation takes a path but no parameters, while the @ApiOperation can be annotated with path parameters but these get appended at the end. In other words, if I write:</p>
  
  <pre><code>@Api(value = "/customers/{CUSTOMER-ID}")
  
  @ApiOperation(httpMethod = "GET")
  @ApiImplicitParams(Array(
  new ApiImplicitParam(name = "ITEM-ID", required = true, dataType = "string", paramType = "path"))
  </code></pre>
  
  <p>I get in the UI only ITEM-ID as testable parameter, while CUSTOMER-ID, while being reported as in { }, is just a string.</p>
  
  <p>I'd like to have something where both are path parameters.</p>
  
  <p>Any idea?</p>