The JNDIView bean needs a massive overhaul to properly display all of the namespaces. I would like to completely move away from class loader based component namespaces. I believe an spi is needed in the naming project that the ENCFactory implements to provide read-only access to all current components for use by admin views like JNDIView. At least this issue is related:
I created https://jira.jboss.org/jira/browse/JBNAME-44 to introduce the spi into naming.
Never mind about JBNAME-44, the legacy ENCFactory is only used for backwards compatibility. A complete view would only be seen from the org.jboss.reloaded.naming classes, so I'll look at introducing a JNDIView class there. I'm not sure if its worth introducing an spi notion at this point.
jboss-reloaded-naming does not define a contract for JavaEE* object creation, so it's effectively unaware of what's flying around. The SimpleJavaEE* classes are just simple prebuilds and aren't even used in the current integration point (jboss-reloaded-naming-deployers).
We could add a registry (JNDIView) into naming and mandate a registration, but I would see that as a bit of scope creep. I think it should rather go into naming-deployers which is in charge of firing up the runtime components and can effectively wire up a registry as well.