I am currently configuring remote JNDI calls for WildFly (version 26.1.2) and have found in the official WildFly documentation that only the JNDI namespace "java:jboss/exported/" is available for clients.
Why is this the case? Is there a good reason for this?
The following is quoted in the documentation https://docs.wildfly.org/26/Developer_Guide.html#remote-ejb-invocations-backed-by-the-wildfly-naming-client-project :
That’s where WildFly will automatically expose the remote views of the EJBs under the java:jboss/exported/ namespace, in addition to the java:global/ java:app/ java:module/ namespaces mandated by the EJB 3.1 spec.
Note that only the java:jboss/exported/ namespace is available to remote clients.
The goal for me is to use the EJB 3.1 standard global namespace in order to not change my current clients (that use the global namespace to connect to other JNDI servers). The namespace is even mentioned in the documentation exactly as my client uses it: java:global/.
