- 15 11月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 05 11月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 04 11月, 2016 4 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14880
-
- 02 11月, 2016 3 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Sebastien Deleuze 提交于
- ScriptedSubscriber has been renamed to Verifier - The Publisher is passed to create() instead of verify() - No more need to specify the generic type explicitly - Version is now sync with reactor-core Issue: SPR-14800
-
- 01 11月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 29 10月, 2016 2 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Juergen Hoeller 提交于
-
- 28 10月, 2016 2 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Sam Brannen 提交于
-
- 27 10月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 25 10月, 2016 1 次提交
-
-
由 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
-
- 21 10月, 2016 4 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Brian Clozel 提交于
-
由 Sebastien Deleuze 提交于
-
由 Brian Clozel 提交于
-
- 20 10月, 2016 3 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
This commit removes the usage of Reactor adapters (about to be moved from Reactor Core to a new Reactor Adapter module). Instead, RxReactiveStreams is now used for adapting RxJava 1 and Flowable methods are used for RxJava 2. Issue: SPR-14824
-
- 12 10月, 2016 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13965
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14541
-
- 06 10月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
This new Reactor Netty release fix a critical issue that could prevent proper connection handling.
-
- 05 10月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 22 9月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 20 9月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 17 9月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14645
-
- 16 9月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Latest dependency updates (Undertow 1.4.3, EhCache 3.1.2, Caffeine 2.3.3, Rome 1.7, Woodstox 5.0.3, Jettison 1.3.8, JRuby 9.1.5.0, RxJava 2.0 RC2, RxNetty 0.5.2 RC4)
-
- 14 9月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 10 9月, 2016 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13965
-
由 Sam Brannen 提交于
-
- 06 9月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
A straight-forward port of the resource handling support in spring-webmvc to spring-web-reactive. Primarily adapting contracts and implementations to use the reactive request and response and the reactive ResourceHttpMessageWriter. Issue: SPR-14521
-
- 03 9月, 2016 2 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14421
-
- 02 9月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 01 9月, 2016 2 次提交
-
-
由 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
-
由 Sebastien Deleuze 提交于
This commit adds support for RxJava 2 Completable, Single, Observable and Flowable types (io.reactivex package). Issue: SPR-14628
-