]
David Lloyd resolved WFLY-9829.
-------------------------------
Resolution: Rejected
The documentation names you refer to are the client-side names which are not covered in
the EJB specification (which does not deal with remote JNDI). The names in the log are
the server-side local names which can be looked up/injected using {{@Resource}} or similar
local JNDI mechanisms. So there is no discrepancy here.
EJB JNDI naming discrepancy between stdout and doc
--------------------------------------------------
Key: WFLY-9829
URL:
https://issues.jboss.org/browse/WFLY-9829
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 12.0.0.Alpha1
Reporter: tommaso borgato
Priority: Minor
On documentation
https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+remote+...
the EJB JNDI name starts with ejb:
{code}
ejb:/jboss-as-ejb-remote-app//CalculatorBean!org.jboss.as.quickstarts.ejb.remote.stateless.RemoteCalculator
{code}
When the server is started (./bin/standalone.sh --server-config=standalone-ha.xml) and
the EJB application is deployed, the logs say:
{code:tile stdout}
15:20:16,327 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473:
JNDI bindings for session bean named 'CalculatorBean' in deployment unit
'deployment "ejb-server.war"' are as follows:
java:global/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:app/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:module/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:global/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:app/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:module/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:jboss/exported/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
{code}
None of them matches the JNDI name mentioned in the documentation.
The JNDI name in the documentation works correctly.