Skip Headers
Oracle® Containers for J2EE Enterprise JavaBeans Developer's Guide
10g (10.1.3.5.0)

Part Number E13981-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

Expanded Deployment

Typically, you package your application into an EAR file before deploying it to OC4J. However, you can deploy an application while still in its expanded directory structure. Because you can skip the packaging step, this is convenient during development and testing. For example, using JDeveloper, you work on an application in its expanded directory structure. Using expanded deployment, you can deploy the expanded directory structure as often as you want without having to re-archive before each deployment.

To configure OC4J for expanded deployment, edit the <OC4J_HOME>\j2ee\home\config\server.xml file and modify the application element for your application to specify a path to the root of the expanded directory for your application. Example 28-3 shows an application element for application myapp with its path attribute set to the root of its expanded directory.

Example 28-3 server.xml for Expanded Deployment

<application-server  ...>
    ...
    <!-- Regular EAR deployment -->
    <application name="app" path="../../home/applications/app.ear" start="true" />

    <!-- Expanded deployment -->
    <application name="myapp" path="C:/projects/myapp" start="true" />
    ...
</application-server>