Skip to content
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

Jakarta EE 9: Enterprise Beans 4.0 always RMIC Compatible #16237

Closed
tkburroughs opened this issue Mar 15, 2021 · 0 comments · Fixed by #17662
Closed

Jakarta EE 9: Enterprise Beans 4.0 always RMIC Compatible #16237

tkburroughs opened this issue Mar 15, 2021 · 0 comments · Fixed by #17662
Assignees
Labels
Epic Used to track Feature Epics that are following the UFO process in:EJB Container jakartaEE9 story team:Blizzard

Comments

@tkburroughs
Copy link
Member

For Enterprise Beans 4.0 (and future versions), generated remote Stub and Tie classes should always be RMIC compatible.

In EJB 3.2, the behavior is configured with the following JVM property with the default being FALSE:

com.ibm.websphere.ejbcontainer.rmicCompatible

For Enterprise Beans 4.0, this JVM property should be ignored, and the behavior should always be rmicCompatible="ALL".

The following needs to be considered:
1 - application server process
2 - application client process

Also, note that the application client process currently makes a call into the server to obtain a list of EJB interfaces that should be generated with RMIC compatible; this call will no longer be required for enterprise beans 4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Used to track Feature Epics that are following the UFO process in:EJB Container jakartaEE9 story team:Blizzard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants