1. 21 Jul, 2017 8 commits
    • dbego's avatar
      Handle possible regexes defensively in NamePatternFilter · c29d1c75
      dbego authored
      Previously, if a name contained part of a regex but wasn't actually
      a regex, a PatternSyntaxException would be thrown and the request
      would fail.
      
      This commit updates NamePatternFilter to catch PatternSyntaxException
      and treat the regex-like input as a name insteead.
      
      See gh-9730
      c29d1c75
    • Andy Wilkinson's avatar
      Polishing · c70cc55d
      Andy Wilkinson authored
      See gh-9827
      c70cc55d
    • Andy Wilkinson's avatar
      Polish javadoc in JsonContentAssert · ece66e1d
      Andy Wilkinson authored
      See gh-9675
      ece66e1d
    • Andy Wilkinson's avatar
      Merge pull request #9675 from Mihhail Lapushkin · a57a7415
      Andy Wilkinson authored
      * gh-9675:
        Polish "Fix JsonContentAssert type safety warnings"
        Fix JsonContentAssert type safety warnings
      a57a7415
    • Andy Wilkinson's avatar
      Polish "Fix JsonContentAssert type safety warnings" · f6727e78
      Andy Wilkinson authored
      - Format code
      - Update an existing test to use the contains method that would
        previously have triggered a type safety warning
      
      Closes gh-9675
      f6727e78
    • Mihhail Lapushkin's avatar
      Fix JsonContentAssert type safety warnings · ae91c846
      Mihhail Lapushkin authored
      Previously, JsonContentAssert returns AbstractMapAssert from
      extractingJsonPathMapValue. This could lead to type safety warnings
      when calling one of the assert's methods with a generic varargs
      parameter such as
      contains(Entry<? extends Object, ? extends Object>...).
      
      This commit replaces the use of both AbstractMapAssert and
      AbstractListAssert with MapAssert and ListAssert respectively. These
      classes use final methods and @SafeVargs args to prevent the
      above-described problem from occurring.
      
      See gh-9675
      ae91c846
    • Andy Wilkinson's avatar
      Revert "Stop auto-config of MethodValidationPP triggering early init" · 15410a40
      Andy Wilkinson authored
      5198fe88. The underlying Framework
      problem that prevents @Lazy from working properly is still there
      in some form or another.
      
      See gh-9416
      15410a40
    • Andy Wilkinson's avatar
      Stop auto-config of MethodValidationPP triggering early init · 5198fe88
      Andy Wilkinson authored
      Previously, if a user's configuration class provided a custom
      Validator bean, that configuration class would be initialized very
      early so that the Validator could be used to create the
      auto-configured MethodValidationPostProcessor. This early
      initialization could problems as it may prevent any of the
      configuration class's dependencies from being post-processed.
      
      This commit updates the injection of the Validator bean to be lazy,
      thereby preventing the creation of the auto-configured
      MethodValidationPostProcessor from triggering early initialization.
      
      Closes gh-9416
      5198fe88
  2. 20 Jul, 2017 7 commits
  3. 19 Jul, 2017 10 commits
  4. 17 Jul, 2017 4 commits
  5. 13 Jul, 2017 3 commits
  6. 10 Jul, 2017 1 commit
  7. 09 Jul, 2017 1 commit
  8. 08 Jul, 2017 6 commits