-
Task
-
Resolution: Done
-
Major
-
None
-
None
Since JBoss EJB 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 4 of remote EJB protocol to indicate EJB client/server is supporting Jakarta EE 9+.
- Activate version 4 of EJB protocol if and only if JBoss EJB 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 or 3 of the protocol.
- causes
-
EJBCLIENT-437 ProtocolV3ObjectResolver is not enabled at the new protocol version
- Resolved
- is blocked by
-
JBMAR-238 Provide support for jakarta<->javax transformation in invocations between servers implementing different specification version
- Resolved
- relates to
-
WFLY-16296 WildFly server based on Jakarta EE API should communicate successfully with previous versions of the server based on Java EE
- Closed