1. 25 2月, 2016 4 次提交
  2. 23 2月, 2016 3 次提交
  3. 19 2月, 2016 6 次提交
  4. 11 2月, 2016 7 次提交
  5. 10 2月, 2016 1 次提交
  6. 05 2月, 2016 5 次提交
  7. 04 2月, 2016 1 次提交
    • S
      Throw exception if TxMgr cannot be retrieved for @Transactional test · 484dd966
      Sam Brannen 提交于
      Prior to this commit, a @Transactional integration test would silently
      be executed without a transaction if the transaction manager could not
      be retrieved from the application context -- for example, it no such
      bean was defined or if multiple beans were present but none satisfied
      the qualifier.
      
      This commit addresses this issue by throwing an IllegalStateException
      if the PlatformTransactionManager cannot be retrieved for a
      @Transactional test.
      
      Issue: SPR-13895
      (cherry picked from commit 6d2b9a01)
      484dd966
  8. 27 1月, 2016 10 次提交
  9. 23 1月, 2016 1 次提交
    • B
      Register prefixed path patterns with FixedVersionStrategy · bcebc9db
      Brian Clozel 提交于
      Prior to this change, configuring a `FixedVersionStrategy` like so
      would configure a single "/js/**" path pattern:
      
      ```
      versionResourceResolver.addFixedVersionStrategy("v1.0.0","/js/**");
      ```
      
      This commit makes sure that for each path pattern, its prefixed version
      is added to the map. For example, the previous configuration also
      adds "/v1.0.0/js/**".
      
      Issue: SPR-13883
      cherry-picked from 84fe46cd
      bcebc9db
  10. 22 1月, 2016 2 次提交
    • B
      Reorder HTTP headers processing in RequestMappingHandlerAdapter · fc34b0c5
      Brian Clozel 提交于
      Prior to this change, the `RequestMappingHandlerAdapter` would first add
      a "Cache-Control" HTTP header to the response (depending on its
      `WebContentGenerator` configuration and `@SessionAttributes` on the
      handler class); then, the Adapter would delegate the actual handler the
      processing of the request.
      This leads to issues, as the handler does not have full control to the
      response and has to deal with pre-existing headers in the response. This
      means that the Adapter and the handler can add incompatible
      Cache-Control directives without knowing it, since one cannot see the
      headers added by the other until the response is committed.
      
      This commit switches the order of execution: first, the handler is
      called (possibly adding HTTP headers), then the RMHA processes the
      response and adds "Cache-Control" directives *only if there's no
      Cache-Control header already defined*.
      
      Issue: SPR-13867
      cherry-picked from 8f1d06f1
      fc34b0c5
    • B
      Fix OutOfBoundsException in ResourceUrlEncodingFilter · a4cb3cf9
      Brian Clozel 提交于
      Prior to this change, the `ResourceUrlEncodingFilter` would try to
      lookup resources URLs as soon as the given URL would be longer than the
      expected context+servlet prefix path. This can lead to
      OutOfBoundsExceptions when the provided URL does not start with that
      prefix and still has the required length.
      
      This commit makes sure that all candidate URLs for resources lookup are
      prefixed with the cached servlet and context path. This underlines the
      fact that the `ResourceUrlEncodingFilter` does not support relative URLs
      for now and delegates to the native servlet implementation in that case.
      
      Issue: SPR-13861
      cherry-picked from 2f6d86b7
      a4cb3cf9