ÂThere are many projects which are probably still using EARs or pulling code in from a third party package that may or may not be updated. It is envisioned that an application either has to use javax or jakartaee but not mix them? For example, in a EAR you have a WAR using JakartaEE and then a JAR with EJBs using javax.Â
Another example, say someone has the both javax and jakartaee interface jars on the class path and accidentally ends up with the imports statements below:
Â Are we expecting that this application would deploy and run successfully? Also, can we still use âejbâ or does that need to be renamed?
Â Are there any concrete classes in the specs which the container would need to have two different implementations of which could cause problems?Â