We need to be able to configure the ee namespace interoperability via model and CLI. Currently it is done by system property.

For more on the ee namespace interoperability: from the remoting POV, a client application hosted in an WildFly server needs to be able to communicate with an application that is transformed and deployed in a EE9 server, even though the legacy server does not have the Jakarta classes and the WildFly 28 server does not have the javax classes in the classpath. This feature was tackled by WFLY-16296.

This RFE is to continue WFLY-16296, by adding configuration to control the interoperability.