org.springframework.web.accept Documentation Differences

This file contains all the changes in documentation in the package org.springframework.web.accept as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

A ContentNegotiationStrategy that uses the path extension of the URL to determine to determine what media types are requested. The path extension is used as follows: first looked Lookup upinin the map of media types provided to the constructor Callconstructor. toIf ServletContext.getMimeType(String) that Usefails, thethe Java Activation framework framework is used as a fallback mechanism.

The presence of the Java Activation framework is detected and enabled automatically enabled automatically but the .setUseJaf(boolean) property may be used toto override that setting. @author Rossen Stoyanchev @since 3.2

Create an instance without any mappings to start with. Mappings may be added later on if any extensions are resolved through ServletContext.getMimeType(String) or through the Java Activation framework.