Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Major
Fix Version/s: 1.0.16.Final
Affects Version/s: None
Labels:
None

Blocked:
False
Blocked Reason:
None
Ready:
False
Git Pull Request:
https://github.com/wildfly/wildfly-naming-client/pull/64, https://github.com/wildfly/wildfly-naming-client/pull/68

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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.

is blocked by

JBMAR-238 Provide support for jakarta<->javax transformation in invocations between servers implementing different specification version

Resolved

is incorporated by

WFLY-17033 Upgrade WildFly Naming Client to 1.0.16.Final

Closed

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

mentioned in: Page Loading...

Assignee:: Richard Opalka

Reporter:: Tomasz Adamski

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/04/21 2:46 PM

Updated:: 2023/01/24 12:44 PM

Resolved:: 2022/09/19 7:12 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates

Hide