1. 21 6月, 2019 3 次提交
    • R
      Package refactoring in rsocket support · c6a2c894
      Rossen Stoyanchev 提交于
      Create annotation.support sub-package and move handler code there. This
      prepares for a future, functional handler (responder) variant and is
      consistent with the package structure under simp.
      c6a2c894
    • B
      PathPattern does not use custom separator · cc05608a
      Brian Clozel 提交于
      Prior to this commit, `PathPattern::extractPathWithinMapping`
      would always use the default path pattern separator `/` when extracting
      the path within the pattern of a matched route.
      
      This commit ensures that `PathPattern` uses the configured separator
      when extracting the path within the matched mapping.
      
      Fixes gh-23168
      cc05608a
    • B
      PathPatternRouteMatcher should use custom separator · 5787fc16
      Brian Clozel 提交于
      Prior to this commit, the `PathPatternRouteMatcher` would always use the
      default path pattern separator when parsing incoming route strings to
      `RouteMatcher.Route` instances.
      When the `PathPatternRouteMatcher` is configured with a
      `PathPatternParser` that has a custom separator (e.g., `.`), then the
      matching algorithm can't match routes against parsed patterns.
      
      This commit ensures that the route matcher uses the configured separator
      at all times.
      
      Fixes gh-23167
      5787fc16
  2. 20 6月, 2019 14 次提交
  3. 19 6月, 2019 3 次提交
  4. 18 6月, 2019 10 次提交
  5. 17 6月, 2019 3 次提交
  6. 14 6月, 2019 5 次提交
  7. 13 6月, 2019 2 次提交
    • S
      Merge branch '5.1.x' · 296220f3
      Stephane Nicoll 提交于
      296220f3
    • S
      Do not override requestContextAttribute with null in UrlBasedViewResolvers · 451cce4f
      Sam Brannen 提交于
      Prior to this commit, if a subclass of
      org.springframework.web.servlet.view.AbstractView or
      org.springframework.web.reactive.result.view.AbstractUrlBasedView
      configured a custom value for the requestContextAttribute, that value
      was overwritten with null whenever the View was dynamically
      instantiated by a UrlBasedViewResolver, and this could lead to
      confusing behavior for users of the View.
      
      This commit addresses this issue by ensuring that the
      UrlBasedViewResolvers in spring-webmvc and spring-webflux do not
      override the requestContextAttribute in a View if the
      UrlBasedViewResolver has not been explicitly configured with a custom
      requestContextAttribute value.
      
      Closes gh-23129
      451cce4f