Skip Headers

# Understanding TopLink Deployment File Creation

Previous

Next

Depending on the type of application you are deploying, you may need to create any of the following deployment files:

- project.xml File

- sessions.xml File

- ejb-jar.xml File

- <J2EE-Container>-ejb-jar.xml File

- toplink-ejb-jar.xml File

TopLink Workbench provides the ability to create deployment files from a TopLink Workbench project (see "Exporting Project Information"). After you build a project, you have two options to create the deployment files:

- Create XML deployment files that require no compiling.

- Create Java source files, which you compile and deploy outside of TopLink Workbench.

Oracle recommends XML deployment because XML files are easier to deploy and troubleshoot than compiled Java files. This approach gives you a very flexible configuration that enables you to make changes safely and easily. XML deployment files do not require third-party applications or compilers to deploy successfully.

Note: If you are using EJB 3.0, you can use annotations to specify most of what you formerly specified in deployment descriptors. Use deployment descriptors to override annotations or specify options not supported by annotations. For more information on what annotations are currently supported, see Oracle Containers for J2EE Enterprise JavaBeans Developer's Guide.