| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Application Development Guide |
Part I Development Tasks and Tools
1. Setting Up a Development Environment
Part II Developing Applications and Application Components
6. Using the Java Persistence API
7. Developing Web Applications
8. Using Enterprise JavaBeans Technology
9. Using Container-Managed Persistence
12. Developing Lifecycle Listeners
13. Developing OSGi-enabled Java EE Applications
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
Accessing EJB Components Using the CosNaming Naming Context
Accessing EJB Components in a Remote GlassFish Server
Naming Environment for Lifecycle Modules
Built-in Factories for Custom Resources
Disabling GlassFish Server V2 Vendor-Specific JNDI Names
Using Application-Scoped Resources
Using a Custom jndi.properties File
A naming service maintains a set of bindings, which relate names to objects. The Java EE naming service is based on the Java Naming and Directory Interface (JNDI) API. The JNDI API allows application components and clients to look up distributed resources, services, and EJB components. For general information about the JNDI API, see http://www.oracle.com/technetwork/java/jndi/index.html. You can also see the JNDI tutorial at http://download.oracle.com/javase/jndi/tutorial/.
The following topics are addressed here:
Note - The Web Profile of the GlassFish Server supports the EJB 3.1 Lite specification, which allows enterprise beans within web applications, among other features. The full GlassFish Server supports the entire EJB 3.1 specification. For details, see JSR 318.
|