Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1798

Implement RxInvokers and proxies for reactive classes in RxJava 1 and 2

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Critical
    • 3.6.0.Final, 4.0.0.Beta4
    • 4.0.0.Beta1, 3.5.0.CR1
    • None
    • None

    Description

      JAX-RS 2.1 permits extensions to support reactive classes in packages like RxJava 1 and RxJava 2 through implementation of the method javax.ws.rs.client.Invocation.Builder.rx():

         public <T extends RxInvoker> T rx(Class<T> clazz);

      This should be done for reactive projects RxJava 1 and 2, and Resteasy proxies should be extended to support the new RxInvokers.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1950 OnComplete callback registered via SseEventSource.register() must be called once

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue RESTEASY-1673 Support CompletionStage resource method return type

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users WFLY-10636 RESTEasy extended async / reactive support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users RESTEASY-1907 Support JDK Flow

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users WFLY-12271 Extend streaming RxInvoker interfaces to allow Response return type

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1885 Fix behavior displayed by streaming RxInvokers with HEAD invocations

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1900 Add client option to permit not reconnecting to SSE servers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1886 Extend streaming RxInvoker interfaces to allow Response return type

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1901 Add ability to associate a MediaType with each data item streaming from server to client

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1903 Support creation by FlowableRxInvoker/ObservableRxInvoker of Flowable/Observable from non-streamed Iterables

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1904 Allow resource methods to stream Iterables over application/x-general-stream streaming mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1906 Allow representation of Exception in SSE stream

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              rsigal@redhat.com Ronald Sigal
              mkopecky@redhat.com Marek Kopecky
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: