1. 16 Mar, 2021 1 commit
  2. 12 Mar, 2021 1 commit
    • Madhura Bhave's avatar
      Fallback to BeanPropertyBindingResult for unbound property validation · df1d1dba
      Madhura Bhave authored
      gh-17424 updated `ValidationBindHandler` so that it would
      only look at bound values when validating. This commit updates
      `ValidationBindHandler` to use Spring Framework's `BeanPropertyBindingResult`.
      This means that for fields that are not bound, JavaBean accessor methods can
      be used to get the value to validate.
      
      Fixes gh-25356
      df1d1dba
  3. 11 Mar, 2021 5 commits
  4. 10 Mar, 2021 4 commits
  5. 09 Mar, 2021 3 commits
  6. 05 Mar, 2021 12 commits
  7. 03 Mar, 2021 5 commits
  8. 01 Mar, 2021 1 commit
  9. 26 Feb, 2021 4 commits
    • Andy Wilkinson's avatar
      Use ResourceConfig customization to register endpoints with Jersey · 8f72ca65
      Andy Wilkinson authored
      Previously, actuator endpoints were registered with Jersey upon
      injection of the ResourceConfig bean into a registrar class rather than
      using a ResourceConfigCustomizer. This was done to fix a problem
      when running the Actuator on a separate port where the main application
      context's customizers were also applied to the management context,
      breaking the singleton contract for those resources. This approach
      meant that the registration could be performed at any point after the
      ResourceConfig had been created. When Jersey's configured as a Filter
      this resulted in the registration failing as the attempt was being made
      after the Filter lifecyle callbacks which make the ResourceConfig
      immutable.
      
      This commit reworks the endpoint registration to be performed using a
      ManagementContextResourceConfigCustomizer, a resource config customizer
      that's only applied to the ResourceConfig that's used by the Actuator.
      When there's a separate management context, this ResourceConfig is
      created by the Actuator's auto-configuration and the management context
      resource config customizers are applied to it during its creation. The
      main application's customizers are not applied. When the actuator is
      using the same context as the main application, this ResourceConfig is
      created by the main application. In this case a
      ResourceConfigCustomizer is defined that delegates to all
      ManagementContextResourceConfigCustomizers, allowing them to register
      the actuator endpoints with the main ResourceConfig.
      
      Fixes gh-25262
      8f72ca65
    • Andy Wilkinson's avatar
      Merge pull request #25446 from dreis2211 · 1e650693
      Andy Wilkinson authored
      * gh-25446:
        Split DeploymentIntegrationTests by container
        Rename DeploymentIntegrationTests
      
      Closes gh-25446
      1e650693
    • dreis2211's avatar
      Split DeploymentIntegrationTests by container · 4ff9e5ed
      dreis2211 authored
      Prior to this commit, every test started a new testcontainer. By splitting the
      tests apart we can make use of static containers that are only instantiated once
      per application (TomEE, Wildfly etc.)
      
      See gh-25446
      4ff9e5ed
    • dreis2211's avatar
      Rename DeploymentIntegrationTests · d55d8d6b
      dreis2211 authored
      See gh-25446
      d55d8d6b
  10. 25 Feb, 2021 4 commits