Ok, the problem is that there is an inconsistency with the standard metadata class processors and the jboss extensions. The org.jboss.metadata.annotation.creator.jboss.AbstractComponentProcessor.process is calling processClass with the JBossEnvironmentRefsGroupMetaData.class as the processorType: | public void process(RemoteEnvironmentRefsGroupMetaData metaData, Class<?> type) | { | // @Resources/@Resource | processClass(metaData, type, JBossEnvironmentRefsGroupMetaData.class); | ... | but the Resource*Processors are only registered for the standard metadata as most of the envionrment metadata is simply standard descriptor stuff. If this is changed to the RemoteEnvironmentRefsGroupMetaData: | public void process(RemoteEnvironmentRefsGroupMetaData metaData, Class<?> type) | { | // @Resources/@Resource | processClass(metaData, type, RemoteEnvironmentRefsGroupMetaData.class); | ... | Then the session context shows up under ResourceEnvironmentReferenceMetaData as expected: 22:57:44,333 INFO [SessionContextAddedToMetadataUnitTestCase] org.jboss.metadata.javaee.spec.ResourceEnvironmentReferenceMetaData@38b735af{context} Assign the issue to Emanuel or Alexy as there are issues with registering jboss specific type processors to deal with this correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166068#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...