Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Regardless whether versioning can be avoided by doing backwards compatible changes (which might not always possible when you are bound by some corporate guidelines or your API clients are implemented in a buggy way and would break even if they should not) the abstracted requirement is an interesting one: </p> <p><strong>How can I do a custom request mapping that does arbitrary evaluations of header values from the request without doing the evaluation in the method body?</strong></p> <p>As described in <a href="https://stackoverflow.com/a/10336769/2615437">this SO answer</a> you actually can have the same <code>@RequestMapping</code> and use a different annotation to differentiate during the actual routing that happens during runtime. To do so, you will have to:</p> <ol> <li>Create a new annotation <code>VersionRange</code>.</li> <li>Implement a <code>RequestCondition&lt;VersionRange&gt;</code>. Since you will have something like a best-match algorithm you will have to check whether methods annotated with other <code>VersionRange</code> values provide a better match for the current request.</li> <li>Implement a <code>VersionRangeRequestMappingHandlerMapping</code> based on the annotation and request condition (as described in the post<a href="https://stackoverflow.com/a/10336769/2615437"> How to implement @RequestMapping custom properties </a>).</li> <li>Configure spring to evaluate your <code>VersionRangeRequestMappingHandlerMapping</code> before using the default <code>RequestMappingHandlerMapping</code> (e.g. by setting its order to 0).</li> </ol> <p>This wouldn't require any hacky replacements of Spring components but uses the Spring configuration and extension mechanisms so it should work even if you update your Spring version (as long as the new version supports these mechanisms).</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to manage REST API versioning with spring?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USxwoker
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to manage REST API versioning with spring?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for adding your comment as an answer xwoker. Up to now is the best one. I have implemented the solution based on the links you mentioned and it's not that bad. The biggest problem will manifest when upgrading to a new version of Spring as it will require to check any changes to the logic behind `mvc:annotation-driven`. Hopefully Spring will provide a version of `mvc:annotation-driven` in which one can define custom conditions.
      singulars
      1. PO
      1. USAugusto
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload