Files
spring-framework/spring-web-reactive
Rossen Stoyanchev 45706422dd InvocableHandlerMethod and arg resolution updates
General improvements e.g. make use of Java 8 Stream. The main reason
for the refactoring however to tighten error handling. To that extent:

InvocableHandlerMethod turns all exceptions into Reactive Streams
error signals, in effect never allowing any Exceptions to bubble up.

HandlerMethodArgumentResolver may throw an Exception for sync resolution
or produce an error signal via the returned Publisher. Either way the
exception is consistently wrapped with helpful method argument details.
For the latter case using a custom mapError operator.

HandlerMethodArgumentResolver no longer needs to return Optional for
nullable argument values. Instead (for now) the defaultIfEmpty operator
of reactor.rx.Stream operator is used to ensure a default constant value
(called "NO_VALUE") is produced. That way an argument resolver may
produce 0..1 values where 0 means it did not resolve to any value and
that results in null passed as the argument value.

If a HandlerMethodArgumentResolver produces more than one value, all
additional values beyond the first one will be ignored with the help
of a custom "first" operator.

As HandlerMethod is invoked within the map operator, checked exceptions
are not allowed but instead of wrapping it in a runtime exception what
we really need is to unwrap the target exception for exception
resolution purposes. To this end concatMap is used to produce a nested
Publisher or an error Publisher with the unwrapped target exception.

Related to that InvocableHandlerMethod now returns
Publisher<HandlerResult> instead of Publisher<Object> so that no longer
needs to be externally mapped from Object to HandlerResult.

InvocableHandlerMethodTests provides tests for the above scenarios and
verifies the details of resulting error signals.
2015-12-07 17:36:58 -05:00
..
2015-08-08 03:57:29 -04:00
2015-07-09 13:42:48 +02:00
2015-08-08 03:57:29 -04:00
2015-08-08 03:57:29 -04:00
2015-09-22 12:27:34 +02:00
2015-09-22 12:14:02 +02:00

Spring Reactive is a sandbox for experimenting on the reactive support intended to be part of Spring Framework 5. For more information about this topic, you can have a look to Intro to Reactive programming and Reactive Web Applications talks.

Downloading Artifacts

Spring Reactive JAR dependency is available from Spring snapshot repository:

  • Repository URL: https://repo.spring.io/snapshot/
  • GroupId: org.springframework.reactive
  • ArtifactId: spring-reactive
  • Version: 0.1.0.BUILD-SNAPSHOT

Building from Source

Spring Reactive uses a Gradle-based build system. In the instructions below, ./gradlew is invoked from the root of the source tree and serves as a cross-platform, self-contained bootstrap mechanism for the build.

You can check the current build status on this Bamboo Spring Reactive build.

Prerequisites

Git and JDK 8 update 20 or later

Be sure that your JAVA_HOME environment variable points to the jdk1.8.0 folder extracted from the JDK download.

Install all spring-* jars into your local Maven cache

./gradlew install

Compile and test; build all jars, distribution zips, and docs

./gradlew build

Contributing

Feel free to send us your feedback on the issue tracker; Pull requests are welcome.

License

The Spring Reactive is released under version 2.0 of the Apache License.