Uploaded image for project: 'WildFly Naming Client'
  1. WildFly Naming Client
  2. WFNC-70

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


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

      Since WildFly NAMING protocol supports 'handshake' kind of messages it is possible to detect other side protocol version before exchanging messages. Because of this we propose to:

      • Introduce new major version 3 of remote NAMING protocol to indicate NAMING client/server is supporting Jakarta EE 9+.
      • Activate version 3 of NAMING protocol if and only if WildFly NAMING client/server is used in Jakarta EE9+ environment.
      • Install javax <-> jakarta class name transformer if and only if Jakarta EE9+ environment is detected and other side is using version 1 or 2 of the protocol.

            ropalka Richard Opalka
            tadamski@redhat.com Tomasz Adamski
            0 Vote for this issue
            1 Start watching this issue