Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer's Guide

- Previous: Deploying a WAR Module
- Next: Deploying a Lifecycle Module

## Deploying an EJB JAR Module

You deploy an EJB JAR module as described in Tools for Deployment.

You can keep the generated source for stubs and ties by adding the `-keepgenerated` flag to the `rmic-options` attribute of the `java-config` element in `domain.xml`. If you include this flag when you deploy the EJB JAR module, the generated source is kept in domain-dir`/generated/ejb/j2ee-apps/`app-name`/`module-name if it is in an application or domain-dir`/generated/ejb/j2ee-modules/`module-name if it is in an individually deployed EJB JAR module. For more information about the `-keepgenerated` flag, see the Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Administration Reference.

Generation of stubs and ties is performed asynchronously, so unless you request their generation during deployment (for example, using the `--retrieve` option of the `asadmin deploy` command), stubs and ties are not guaranteed to be available immediately after deployment. You can use the `asadmin get-client-stubs` command to retrieve the stubs and ties whether or not you requested their generation during deployment. For details, see the Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Reference Manual.

- Previous: Deploying a WAR Module
- Next: Deploying a Lifecycle Module

- © 2010, Oracle Corporation and/or its affiliates