1. 22 4月, 2021 1 次提交
    • C
      Avoid exceptions when evaluating validation hints · e7cbe237
      Christoph Dreis 提交于
      Prior to this commit, evaluating validation hints for
      @javax.validation.Valid caused exceptions being raised when getting the
      value of this annotation, which does not exist. Bypassing
      AnnotationUtils.getValue() in those cases can improve performance by
      avoiding the cost incurred by raising exceptions.
      
      See gh-26787
      e7cbe237
  2. 02 9月, 2020 1 次提交
  3. 29 8月, 2020 2 次提交
  4. 07 8月, 2020 1 次提交
  5. 23 3月, 2019 1 次提交
  6. 22 3月, 2019 1 次提交
  7. 18 7月, 2018 1 次提交
  8. 17 7月, 2018 1 次提交
  9. 02 2月, 2018 1 次提交
  10. 18 10月, 2017 1 次提交
  11. 28 9月, 2017 1 次提交
    • J
      Revised handling of missing data class arguments · ec345bf1
      Juergen Hoeller 提交于
      Includes unified detection of Kotlin's optional parameters in MethodParameter.isOptional(), reduces BeanUtils.findPrimaryConstructor to Kotlin semantics (for reuse in AutowiredAnnotationBeanPostProcessor), and finally introduces a common KotlinDetector delegate with an isKotlinType(Class) check.
      
      Issue: SPR-15877
      Issue: SPR-16020
      ec345bf1
  12. 18 8月, 2017 1 次提交
  13. 17 8月, 2017 2 次提交
  14. 20 7月, 2017 1 次提交
  15. 30 6月, 2017 1 次提交
  16. 07 6月, 2017 1 次提交
    • J
      Consistent use of @Nullable across the codebase (even for internals) · f813712f
      Juergen Hoeller 提交于
      Beyond just formally declaring the current behavior, this revision actually enforces non-null behavior in selected signatures now, not tolerating null values anymore when not explicitly documented. It also changes some utility methods with historic null-in/null-out tolerance towards enforced non-null return values, making them a proper citizen in non-null assignments.
      
      Some issues are left as to-do: in particular a thorough revision of spring-test, and a few tests with unclear failures (ignored as "TODO: NULLABLE") to be sorted out in a follow-up commit.
      
      Issue: SPR-15540
      f813712f
  17. 24 3月, 2017 1 次提交
  18. 18 2月, 2017 1 次提交
  19. 05 7月, 2016 1 次提交
  20. 24 3月, 2016 1 次提交
  21. 27 1月, 2016 2 次提交
  22. 20 2月, 2015 1 次提交
  23. 11 2月, 2015 1 次提交
  24. 25 11月, 2014 1 次提交
  25. 25 9月, 2014 1 次提交
  26. 14 5月, 2013 1 次提交
  27. 02 1月, 2013 1 次提交
  28. 29 12月, 2012 1 次提交
  29. 22 8月, 2012 1 次提交
    • R
      Allow Errors after @RequestBody and @RequestPart · af156163
      Rossen Stoyanchev 提交于
      An @RequestBody or an @RequestPart argument can now be followed by an
      Errors/BindingResult argument making it possible to handle validation
      errors (as a result of an @Valid annotation) locally within the
      @RequestMapping method.
      
      Issue: SPR-7114
      af156163
  30. 11 5月, 2012 1 次提交
    • R
      Fix issue with resolving Errors controller argument · c499df23
      Rossen Stoyanchev 提交于
      The ErrorsMethodArgumentResolver expects the preceding @ModelAttribute
      in the controller method signature to be the last one added in the
      model -- an assumption that can break if a model attribute is added
      earlier (e.g. through a @ModelAttribute method) and more attributes
      are added as well. This fix ensures when an @ModelAttribute is resolved
      as a controller method argument it has the highest index in the model.
      
      Issue: SPR-9378
      c499df23
  31. 31 1月, 2012 1 次提交
    • C
      Rename modules {org.springframework.*=>spring-*} · 02a4473c
      Chris Beams 提交于
      This renaming more intuitively expresses the relationship between
      subprojects and the JAR artifacts they produce.
      
      Tracking history across these renames is possible, but it requires
      use of the --follow flag to `git log`, for example
      
          $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history up until the renaming event, where
      
          $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history for all changes to the file, before and after the
      renaming.
      
      See http://chrisbeams.com/git-diff-across-renamed-directories
      02a4473c
  32. 11 1月, 2012 1 次提交
    • C
      Polish "Support flash attrs..." and related classes · d7d1b495
      Chris Beams 提交于
       - Eliminate trailing whitespace
      
       - Update long method signatures to follow framework whitespace
         conventions
      
         Based on the following search,
      
             $ git grep -A3 '^.public .* .*([^\{;]*$' */src/main
      
         the strong convention throughout the framework when dealing with
         methods having long signatures (i.e. many parameters) is to break
         immediately after the opening paren, indent two tabs deeper and break
         lines around 90 characters as necessary. Such signatures should also
         be followed by a newline after the opening curly brace to break
         things up visually.
      
         The files edited in this commit had a particularly different style of
         intenting arguments to align with each other vertically, but the
         alignment only worked if one's tabstop is set at four spaces.
         When viewed at a different tabstop value, the effect is is jarring,
         both in that it is misaligned and significantly different from most
         of the framework. The convention described above reads well at any
         tabstop value.
      d7d1b495
  33. 13 12月, 2011 1 次提交
  34. 10 12月, 2011 1 次提交
  35. 03 12月, 2011 1 次提交
  36. 05 11月, 2011 1 次提交
  37. 24 9月, 2011 1 次提交