Generated by
JDiff

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.

Class ContentNegotiationManager, void addFileExtensionResolvers(MediaTypeFileExtensionResolver[])

Add MediaTypeFileExtensionResolver instances.

Note that some ContentNegotiationStrategy implementations also implement MediaTypeFileExtensionResolver and the class constructor accepting the former will also detect implementations of the latter. Therefore you only need to use this method to register additional instances. @param resolvers one or more resolvers

Class ContentNegotiationManager, List<MediaType> resolveMediaTypes(NativeWebRequest)

Delegate to all configured ContentNegotiationStrategy instances until one returns a non-empty list. @param requestwebRequest the current request @return the requested media types or an empty list, never {@code null} @throws HttpMediaTypeNotAcceptableException if the requested media types cannot be parsed

Class ContentNegotiationManagerFactoryBean

A factory providing convenient access to a {@code ContentNegotiationManager} configured with one or more ContentNegotiationStrategy instances.

By default strategies for checking the extension of the request path and the {@code Accept} header are registered. The path extension check will perform lookups through the ServletContext and the Java Activation Framework (if present) unless #setMediaTypes(MapProperties) media types are configured. @author Rossen Stoyanchev @since 3.2

Class ContentNegotiationManagerFactoryBean, void setFavorParameter(boolean)

Indicate whether a request parameter should be used to determine the requested media type with the 2nd highest priority, i.e. after path extensions but before the {@code Accept} header.

The default value is {@code false}. If set to to {@code true}, a request for {@code /hotels?format=pdf} will be interpreted as a request for {@code "application/pdf"} regardless of the {@code Accept} header.

To use this option effectively you must also configure the MediaType type mappings via .setMediaTypes(MapProperties). @see #setParameterName(String)

Class ContentNegotiationManagerFactoryBean, void setUseJaf(boolean)

Indicate whether to use the Java Activation Framework as a fallback option to map from file extensions to media types. This is used only when .setFavorPathExtension(boolean) is set to {@code true}.

The default value is {@code true}. @see #parameterName @see #setMediaTypes(MapProperties)


Class ContentNegotiationStrategy, List<MediaType> resolveMediaTypes(NativeWebRequest)

Resolve the given request to a list of media types. The returned list is ordered by specificity first and by quality parameter second. @param requestwebRequest the current request @return the requested media types or an empty list, never {@code null} @throws HttpMediaTypeNotAcceptableException if the requested media types cannot be parsed