| 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
Introducing the Application Client Container
Developing Clients Using the ACC
To Access an EJB Component From an Application Client
To Access a JMS Resource From an Application Client
Enabling and Disabling Java Web Start
Downloading and Launching an Application Client
Signing JAR Files Used in Java Web Start
Vendor Icon, Splash Screen, and Text
Running an Application Client Using the appclient Script
Using the package-appclient Script
Connecting to a Remote EJB Module Through a Firewall
Using Libraries with Application Clients
Developing Clients Without the ACC
To access an EJB component from a stand-alone client
To access an EJB component from a server-side module
To access a JMS resource from a stand-alone client
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
16. Using the Java Naming and Directory Interface
This chapter describes how to develop, assemble, and deploy Java clients.
The following topics are addressed here:
Note - The Web Profile of the OracleGlassFish 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.
Accordingly, the Application Client Container is supported only in the full GlassFish Server, not in the Web Profile.
JMS resources are supported only in the full GlassFish Server, not in the Web Profile. See Chapter 17, Using the Java Message Service.
|