1. 29 11月, 2016 1 次提交
    • R
      Further refactoring of ReactiveAdapter/Registry · 5651c218
      Rossen Stoyanchev 提交于
      Simplify getAdapterFrom/To into a single getAdapter method that looks
      for an exact match by type first and then isAssignableFrom.
      
      Also expose shortcut methods in ReactiveAdapter to minimize the need
      for access to the ReactiveTypeDescriptor.
      
      Issue: SPR-14902
      5651c218
  2. 28 11月, 2016 2 次提交
    • R
      Refactor ReactiveAdapter hierarchy · 52096ab8
      Rossen Stoyanchev 提交于
      Collapse ReactiveAdapter hierarchy into a single class that simply
      delegates to functions for converting to/from a Publisher.
      
      A private ReactorAdapter extension automaticlaly wraps adapted,  "raw"
      Publisher's as Flux or Mono depending on the semantics of the target
      reactive type.
      
      Issue: SPR-14902
      52096ab8
    • R
      Improved reactive type descriptor support · 2e7d16df
      Rossen Stoyanchev 提交于
      ReactiveTypeDescriptor is now a top-level type with named constructors.
      It also contains and provides a getter for the actual type.
      
      Issue: SPR-14902
      2e7d16df
  3. 04 11月, 2016 2 次提交
  4. 03 11月, 2016 1 次提交
  5. 02 11月, 2016 1 次提交
  6. 31 10月, 2016 1 次提交
  7. 29 10月, 2016 1 次提交
  8. 25 10月, 2016 2 次提交
    • S
      Add support for RxJava 2 Maybe type · 20759327
      Sebastien Deleuze 提交于
      Issue: SPR-14843
      20759327
    • B
      Refactor tests with ScriptedSubscriber · 99a32108
      Brian Clozel 提交于
      Reactor recently added the `ScriptedSubscriber` in its new
      `reactor-addons` module. This `Subscriber` revissits the previous
      `TestSubscriber` with many improvements, including:
      
      * scripting each expectation
      * builder API that guides you until the final verification step
      * virtual time support
      
      This commit refactor all existing tests to use this new
      infrastructure and removed the `TestSubscriber` implementation.
      
      Issue: SPR-14800
      99a32108
  9. 21 10月, 2016 2 次提交
  10. 18 10月, 2016 1 次提交
  11. 20 9月, 2016 2 次提交
    • B
      Add ResourceRegionEncoder · 55d6f88d
      Brian Clozel 提交于
      This commit adds the necessary infrastructure for the support of HTTP
      Range requests. The new `ResourceRegionEncoder` can write
      `ResourceRegion` objects as streams of bytes.
      
      The `ResourceRegionEncoder` relies on an encoding hint
      `BOUNDARY_STRING_HINT`. If present, the encoder infers that multiple
      `ResourceRegion`s should be encoded and that the provided boundary
      String should be used to separate ranges by mime boundaries.
      If that hint is absent, only a single resource region is encoded.
      
      Issue: SPR-14664
      55d6f88d
    • S
      Do not provide hints for can*() methods anymore · 38f3d12e
      Sebastien Deleuze 提交于
      Issue: SPR-14557
      38f3d12e
  12. 17 9月, 2016 1 次提交
  13. 15 9月, 2016 4 次提交
  14. 12 9月, 2016 1 次提交
  15. 01 9月, 2016 2 次提交
    • S
      Support for candidate components index · dcade06f
      Stephane Nicoll 提交于
      This commit adds a "spring-context-indexer" module that can be added to
      any project in order to generate an index of candidate components defined
      in the project.
      
      `CandidateComponentsIndexer` is a standard annotation processor that
      looks for source files with target annotations (typically `@Component`)
      and references them in a `META-INF/spring.components` generated file.
      
      Each entry in the index is the fully qualified name of a candidate
      component and the comma-separated list of stereotypes that apply to that
      candidate. A typical example of a stereotype is `@Component`. If a
      project has a `com.example.FooService` annotated with `@Component` the
      following `META-INF/spring.components` file is generated at compile time:
      
      ```
      com.example.FooService=org.springframework.stereotype.Component
      ```
      
      A new `@Indexed` annotation can be added on any annotation to instructs
      the scanner to include a source file that contains that annotation. For
      instance, `@Component` is meta-annotated with `@Indexed` now and adding
      `@Indexed` to more annotation types will transparently improve the index
      with additional information. This also works for interaces or parent
      classes: adding `@Indexed` on a `Repository` base interface means that
      the indexed can be queried for its implementation by using the fully
      qualified name of the `Repository` interface.
      
      The indexer also adds any class or interface that has a type-level
      annotation from the `javax` package. This includes obviously JPA
      (`@Entity` and related) but also CDI (`@Named`, `@ManagedBean`) and
      servlet annotations (i.e. `@WebFilter`). These are meant to handle
      cases where a component needs to identify candidates and use classpath
      scanning currently.
      
      If a `package-info.java` file exists, the package is registered using
      a "package-info" stereotype.
      
      Such files can later be reused by the `ApplicationContext` to avoid
      using component scan. A global `CandidateComponentsIndex` can be easily
      loaded from the current classpath using `CandidateComponentsIndexLoader`.
      
      The core framework uses such infrastructure in two areas: to retrieve
      the candidate `@Component`s and to build a default `PersistenceUnitInfo`.
      Rather than scanning the classpath and using ASM to identify candidates,
      the index is used if present.
      
      As long as the include filters refer to an annotation that is directly
      annotated with `@Indexed` or an assignable type that is directly
      annotated with `@Indexed`, the index can be used since a dedicated entry
      wil be present for that type. If any other unsupported include filter is
      specified, we fallback on classpath scanning.
      
      In case the index is incomplete or cannot be used, The
      `spring.index.ignore` system property can be set to `true` or,
      alternatively, in a "spring.properties" at the root of the classpath.
      
      Issue: SPR-11890
      dcade06f
    • S
      Add support for RxJava 2 · 48d67a24
      Sebastien Deleuze 提交于
      This commit adds support for RxJava 2 Completable,
      Single, Observable and Flowable types (io.reactivex package).
      
      Issue: SPR-14628
      48d67a24
  16. 31 8月, 2016 2 次提交
  17. 29 8月, 2016 1 次提交
  18. 26 8月, 2016 3 次提交
  19. 25 8月, 2016 1 次提交
    • B
      Add RFC5987 support for HTTP header field params · f2faf84f
      Brian Clozel 提交于
      This commit adds support for HTTP header field parameters encoding, as
      described in RFC5987.
      Note that the default implementation still relies on US-ASCII encoding,
      as the latest rfc7230 Section 3.2.4 says that:
      
      > Newly defined header fields SHOULD limit their field values to
        US-ASCII octets
      
      Issue: SPR-14547
      f2faf84f
  20. 18 8月, 2016 1 次提交
  21. 10 8月, 2016 1 次提交
  22. 08 8月, 2016 1 次提交
    • S
      Anticipate reactor.test.TestSubscriber removal · 5531e807
      Sebastien Deleuze 提交于
      reactor.test.TestSubscriber will not be part of Reactor Core
      3.0.0 since it needs to be refactored to fit all the needs
      expressed by the users. It is likely to be back later in one
      of the Reactor Core 3.0.x releases.
      
      This commit anticipate this removal by temporarily copying
      TestSubscriber in spring-core test classes. As soon as
      the new TestSubscriber will be available in Reactor Core,
      Spring Framework reactive tests will use it again.
      5531e807
  23. 26 7月, 2016 2 次提交
  24. 25 7月, 2016 2 次提交
  25. 23 7月, 2016 2 次提交