@ -49,6 +49,11 @@ This strategy resolves the API version from a request. The WebFlux config provid
@@ -49,6 +49,11 @@ This strategy resolves the API version from a request. The WebFlux config provid
options to resolve from a header, query parameter, media type parameter,
or from the URL path. You can also use a custom `ApiVersionResolver`.
NOTE: The path resolver always resolves the version from the specified path segment, or
raises `InvalidApiVersionException` otherwise, and therefore it cannot yield to other
@ -49,6 +49,11 @@ This strategy resolves the API version from a request. The MVC config provides b
@@ -49,6 +49,11 @@ This strategy resolves the API version from a request. The MVC config provides b
options to resolve from a header, query parameter, media type parameter,
or from the URL path. You can also use a custom `ApiVersionResolver`.
NOTE: The path resolver always resolves the version from the specified path segment, or
raises `InvalidApiVersionException` otherwise, and therefore it cannot yield to other
@ -47,17 +51,18 @@ public class PathApiVersionResolver implements ApiVersionResolver {
@@ -47,17 +51,18 @@ public class PathApiVersionResolver implements ApiVersionResolver {
@ -45,14 +49,14 @@ public class PathApiVersionResolver implements ApiVersionResolver {
@@ -45,14 +49,14 @@ public class PathApiVersionResolver implements ApiVersionResolver {