Skip to content
RxJava 2 utilities.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
rxjava-support Migrate from TestNG to Junit 5 (#27) Nov 20, 2018
.gitignore First commit Feb 5, 2018
.travis.yml Support Error Prone on Java 8-11 (#32) Nov 19, 2018
LICENSE.md Prepare for publication to Maven Central (#10) Mar 12, 2018
README.md
pom.xml

README.md

Picnic Reactive Support

Build Status Maven Central Coverage SonarCloud Quality Gate SonarCloud Bugs SonarCloud Vulnerabilities SonarCloud Debt Ratio BCH compliance

A collection of Reactive Programming (RxJava and Reactor) utilities forged and implemented in the Picnic backend.

How to Install

Artifacts are hosted on Maven's Central Repository:

Gradle

dependencies {
    compile 'tech.picnic.reactive-support:rxjava-support:0.0.1'
}

Maven

<dependency>
    <groupId>tech.picnic.reactive-support</groupId>
    <artifactId>rxjava-support</artifactId>
    <version>0.0.1</version>
</dependency>

How To Use

This library contains a number of useful RxJava utilities. Listed below are example usages of some notable cases.

RxJava Thread Context Propagation

To propagate thread-local contexts to RxJava Scheduler thread pools you can create your own RxThreadLocal containing a value fetcher Supplier<T> (that is called before a Runnable is scheduled by a Scheduler), a context setter Consumer<T> that sets the context on the new RxJava Scheduler thread, and an unset Consumer<T> which reinstates the original context after the Scheduler has finished executing the scheduled Runnable. The same Consumer<T> can be used to both configure and restore the context.

Please see the code below for an example usage with initialisation in ServletContextListener, where we propagate the contents of SLF4J's MDC map and Spring's SecurityContextHolder. This way that we can retain meaningful logging attributes and execute secured methods from within RxJava-scheduled actions.

@WebListener
public final class RxServletContextListener implements ServletContextListener {
    @Override
    public void contextInitialized(ServletContextEvent sce) {
        RxThreadLocal<?> mdcPropagation =
                RxThreadLocal.from(
                        MDC::getCopyOfContextMap,
                        m -> {
                            if (m != null) {
                                MDC.setContextMap(m);
                            } else {
                                MDC.clear();
                            }
                        });
        RxThreadLocal<?> securityContextPropagation =
                RxThreadLocal.from(
                        SecurityContextHolder::getContext, SecurityContextHolder::setContext);
        PicnicRxPlugins.configureContextPropagation(mdcPropagation, securityContextPropagation);
    }

    @Override
    public void contextDestroyed(ServletContextEvent sce) {
        PicnicRxPlugins.unsetContextPropagation();
        Schedulers.shutdown();
    }
}

RetryStrategy

The RetryStrategy type is meant to be used in conjunction with Flowable#retryWhen to create and define more advanced retry strategies. For example:

someFlowable
    .retryWhen(
         RetryStrategy.ifInstanceOf(TooManyRequestsException.class)
             .withBackoffScheduler(Schedulers.io())
             .exponentialBackoff(Duration.ofMillis(500)
             .build())

RxSpring4Util

This is a utility that can be used to convert RxJava reactive types into asynchronous Spring web types. See below for a number of example usages.

Converting Spring DeferredResult:

@PostMapping("/endpoint")
public DeferredResult<Integer> someEndpoint() {
    return Single.just(1).to(singleToDeferredResult());
}

@GetMapping("/another")
public DeferredResult<ImmutableSet<Integer>> someOtherEndpoint() {
    return Flowable.just(1, 2, 3).to(publisherToDeferredResult(ImmutableSet::copyOf));
}

Converting to Spring's SseEmitter:

@GetMapping("/sse")
public SseEmitter sseEndpoint() {
    return Flowable.just(1, 2, 3).to(publisherToSse());
}

Contributing

Contributions are welcome! Feel free to file an issue or open a pull request.

When submitting changes, please make every effort to follow existing conventions and style in order to keep the code as readable as possible. New code must be covered by tests. As a rule of thumb, overall test coverage should not decrease. (There are exceptions to this rule, e.g. when more code is deleted than added.)

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.