From the AS Naming developer point of view I'm more into 3) but standard JNDI api failing like in this issue could make 1) more desirable, even if more dangerous.

NoSuchMethodError pushOwner(ServiceTarget,ServiceName) ------------------------------------------------------ Key: WFLY-963 URL: https://issues.jboss.org/browse/WFLY-963 Project: WildFly Issue Type: Bug Components: Naming Reporter: Jeff Yu Assignee: Eduardo Martins In the JBoss AS-7.1.1.Final, I used the following code to do the JNDI binding/unbinding from the modules (not deployed in the deployment folder). public class JndiRegistry { private static final Log LOG= LogFactory.getLog(JndiRegistry.class); public static void bindToJndi(String name, Object object) { ServiceTarget serviceTarget = CurrentServiceContainer.getServiceContainer(); if (serviceTarget != null) { WritableServiceBasedNamingStore.pushOwner(serviceTarget); try { InitialContext context = new InitialContext(); context.bind(name, object); } catch (NamingException e) { LOG.error("Error in binding the object in JNDI."); } } } public static void unbindFromJndi(String name){ ServiceTarget serviceTarget = CurrentServiceContainer.getServiceContainer(); if (serviceTarget != null) { WritableServiceBasedNamingStore.pushOwner(serviceTarget); try { InitialContext context = new InitialContext(); context.unbind(name); } catch (NamingException e) { LOG.error("Error in unbinding the object from JNDI."); } } } } With the EAP 6.1.0.Alpha, I am getting the error of " Caused by: java.lang.NoSuchMethodError: org.jboss.as.naming.WritableServiceBasedNamingStore.pushOwner(Lorg/jboss/msc/service/ServiceTarget;[Lorg/jboss/msc/service/ServiceName;)V",