| Exit Print View | |
Sun GlassFish Enterprise Server v3 Application Development Guide |
|
|
|
Part I Development Tasks and Tools
1. Setting Up a Development Environment
Using the Java Optional Package Mechanism
Using the Endorsed Standards Override Mechanism
Application-Specific Class Loading
Circumventing Class Loader Isolation
Packaging the Client JAR for One Application in Another Application
To Package the Client JAR for One Application in Another Application
3. Using Ant with Enterprise Server
Part II Developing Applications and Application Components
7. Using the Java Persistence API
8. Developing Web Applications
9. Using Enterprise JavaBeans Technology
10. Using Container-Managed Persistence
13. Developing Lifecycle Listeners
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
16. Using the Java Naming and Directory Interface
Understanding Sun GlassFish Enterprise Server class loaders can help you determine where to place supporting JAR and resource files for your modules and applications. For general information about J2SE class loaders, see Understanding Network Class Loaders.
In a JVM implementation, the class loaders dynamically load a specific Java class file needed for resolving a dependency. For example, when an instance of java.util.Enumeration needs to be created, one of the class loaders loads the relevant class into the environment. This section includes the following topics:
Note - The Web Profile of the Enterprise Server supports the EJB 3.1 Lite specification, which allows enterprise beans within web applications, among other features. The full Enterprise Server supports the entire EJB 3.1 specification. For details, see JSR 318.
|
|
