Uploaded image for project: 'WildFly EJB HTTP Client'
  1. WildFly EJB HTTP Client
  2. WEJBHTTP-79

Adapt wildfly-http-client to work correctly in EAP7<->EAP8 invocation scenarios

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 1.1.14.Final
    • None
    • None

      Since WildFly HTTP protocol doesn’t support 'handshake' kind of messages it is not possible to detect other side protocol version in advance. Because of this we propose to:

      • Install javax <-> jakarta class name transformer if and only if WildFly HTTP client/server is used in Jakarta EE9+ environment.
      • Always translate all jakarta EE types to javax EE types regardless if other side supports Jakarta EE9+ environment.

              ropalka Richard Opalka
              tadamski@redhat.com Tomasz Adamski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: