-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing JavaEE <-> JakartaEE interoperability scenarios #543
Conversation
javax/src/main/java/org/jboss/ejb/protocol/remote/EJBClientChannel.java
Outdated
Show resolved
Hide resolved
javax/src/main/java/org/jboss/ejb/protocol/remote/EJBServerChannel.java
Outdated
Show resolved
Hide resolved
…ios. This introduces new EJB protocol version number 4. Protocol versions 1 2 and 3 mean JBoss EJB Client runs in JavaEE environment. Protocol versions 4 and above mean JBoss EJB Client runs in JakartaEE environment.
@@ -23,7 +23,11 @@ | |||
*/ | |||
final class Protocol { | |||
|
|||
public static final int LATEST_VERSION = 3; | |||
static final int JAVAEE_PROTOCOL_VERSION = 3; | |||
static final int JAKARTAEE_PROTOCOL_VERSION = 4; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really would like to validate if this is necessary or if a simple attribute in the remote outbound connection could be used to indicate the need for transformation without an upgrade in the protocol version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is really necessary. Otherwise Jakarta EE side wouldn't know if communicating oposite side runs in Java EE or in Jakarta EE environment @fl4via .
https://issues.redhat.com/browse/EJBCLIENT-419