Appendix A. JNDI namespaces

This appendix covers
  • Understanding the Enterprise Naming Context
  • Examining common JNDI namespaces

As we discussed in chapter 7, EJBs are automatically bound into a JNDI server when they’re deployed to the application server. The JBoss JNDI naming server is called JBossNS. Every application server binds beans into naming contexts of the application server’s own choice. For example, as you saw in chapter 7, if you deploy an EAR file, JBoss will bind the beans into a context relative to the EAR file name. JBoss uses this convention, but other application servers may or may not use different strategies. In this appendix, we’ll explore how JBoss does JNDI binding and how to generically bind your applications in JNDI, ...

Get JBoss in Action now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial