-
Enhancement
-
Resolution: Done
-
Major
-
12.0.0.Final
-
None
It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
<iiop enable-by-default="true" use-qualified-name="true"/>
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
Something like this when use-qualified-name="true"
IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: iiop-eap7/HelloSessionBean
or use-qualified-name="false"
IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: HelloSessionBean
- is cloned by
-
JBEAP-19329 [GSS](7.3.z) Include EJB's IIOP Binding when EJB is deployed logging
- Closed
- relates to
-
WFLY-13384 Add IIOP Naming View Management Command
- Open