To enable the new Application Component Environment Namespaces I've created a component in Reloaded: jboss-reloaded-naming. [1] With JBNAME-37 [2] the setting up of java:comp itself can be disabled in the naming server itself. AS then needs to delegate this to org.jboss.reloaded.naming.service.NameSpaces. [3] NameSpaces will set up the four namespaces defined in the JavaEE 6 spec. java:global will be a simple LinkRef to the root. java:app, java:module and java:comp will be ObjectFactories return the scoped context based on the current component. [4] For a JavaEE container to be obtain a JavaEEComponent a couple of deployers need to be created. An AppDeployer which will setup java:global/<app-name> and store that Context into a JavaEEApplication. This will be attached to the deployment unit. A ModuleDeployer which creates java:app/<module-name> and again attach it to the deployment unit. A ComponentDeployer which in case of a Web Archive will create a LinkRef to java:module, otherwise it will create a new context. Either LinkRef or Context will be bound under java:module/<component-name>. (Note to self: the <module-name> includes the path structure within the EAR.) After this we can think about setting up a complete JSR-250 injection environment into java:comp via a standalone deployer. 1. https://jira.jboss.org/jira/browse/RELOADED-9 2. https://jira.jboss.org/jira/browse/JBNAME-37 3. http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/reloaded/trun... 4. http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/reloaded/trun... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269944#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...