1. 06 Apr, 2018 1 commit
  2. 26 Mar, 2018 2 commits
    • Dave Syer's avatar
      Update README · 7e53a744
      Dave Syer authored
      7e53a744
    • Dave Syer's avatar
      Convert Consumer<Foo> to Function<Flux<Foo>,Mono<Void>> · 5aeba1ea
      Dave Syer authored
      This results in a better experience for users because the consumer
      that they write is only applied to a Flux that is subscribed to
      by the framework once. It gives better control over the flow of
      foos, e.g. if some component wants to subscribe on a thread.
      5aeba1ea
  3. 21 Mar, 2018 1 commit
    • Dave Syer's avatar
      Inspect bean class if it is available · a1b624b2
      Dave Syer authored
      Avoids instantiating beans if not necessary, and allows user to
      provide Function as a @SpringBootApplication (for instance), or
      more generally as a source to the application context (as opposed
      to being component scanned).
      a1b624b2
  4. 20 Mar, 2018 2 commits
  5. 18 Mar, 2018 1 commit
  6. 16 Mar, 2018 6 commits
  7. 15 Mar, 2018 2 commits
  8. 09 Mar, 2018 1 commit
  9. 02 Mar, 2018 1 commit
  10. 01 Mar, 2018 1 commit
  11. 28 Feb, 2018 3 commits
  12. 27 Feb, 2018 1 commit
  13. 26 Feb, 2018 5 commits
  14. 24 Feb, 2018 1 commit
  15. 23 Feb, 2018 5 commits
  16. 21 Feb, 2018 1 commit
  17. 20 Feb, 2018 1 commit
  18. 16 Feb, 2018 2 commits
    • Dave Syer's avatar
      8cd26759
    • Dave Syer's avatar
      Support for isolated class loaders extended to cover more functions · 1b624c35
      Dave Syer authored
      Functions with Flux and Message (as well as POJOs and Flux of POJO
      which were already supported) should now work if they are created in
      an isolated class loader. Preconditions:
      
      * The class loaders must have the reactor-core (and reactive-streams)
      shared between the app and the function. Practically speaking this means
      there has to be a parent class loader with just reactive types, and
      sibling children for the app and the function. This is not a new
      requirement (it was needed for Flux of POJO anyway).
      
      * Message types are handled reflectively, so they don't have to be in a
      shared class loader. But they do have to be  on the class path on
      both sides (obviously).
      1b624c35
  19. 14 Feb, 2018 2 commits
  20. 09 Feb, 2018 1 commit