Exporting Archive Files

Your Workshop for WebLogic projects can be exported into archive files:

You can:

• Export an Enterprise Application Project to an EAR
• Export a Web Project to a WAR
• Export a Utility Project to a JAR
• Export an EJB Project to an EJB JAR
• Export Controls in a Utility Project to a Control JAR

Note that options on the Export dialog that are not described in this documentation do not apply to Workshop for WebLogic projects. For example, you can use the Archive and JAR file options of the Export dialog to create JAR files for EJB and web projects. However this is only a useful feature for creating utility JAR files for sharing code.

How to Export an Enterprise Application Project to an EAR

To export an EAR project to an EAR file:

1. Right click anywhere on the Project Explorer view and choose Export from the menu.
2. Click EAR file and click Next.

   

3. Use the pulldown to select the EAR project in the EAR application box. Use the Browse button to specify the location where the new EAR file will be located.

   

   If the file already exists, you must check the Overwrite existing file selection to replace the existing file.

   Normally the Export source files option is unchecked. If you wish to include the Java source files in your archive, you must check this option. The most common reason to export an EAR file is to deploy for production, and in that case, the source files should not be included. Include the source files only if you wish to view/edit source at the destination.

4. Click Finish to create the EAR file.

How to Export a Web Project to a WAR

To export a web project to a WAR file:

1. Right click anywhere on the Project Explorer view and choose Export from the menu.
2. Click WAR file and click Next.

   

3. Use the pulldown to select the web project in the Web module box. Use the Browse button to specify the location of the WAR file.

   

   If the file already exists, you must check the Overwrite existing file selection to replace the existing file.

   Normally the Export source files option is unchecked. If you wish to include the Java source files in your archive, you must check this option. The most common reason to export a WAR file is to deploy for production, and in that case, the source files should not be included. Include the source files only if you wish to view/edit source at the destination.

4. Click Finish to create the WAR file.

How to Export a Utility Project to a JAR

Note that if you use this process to create a JAR file from a utility project, then the controls within the JAR will not appear in the IDE correctly (although they will work correctly). You can also export the controls in a utility project to a control JAR.

To export a utility project to a JAR file:

1. Right click on the name of the utility project in the Project Explorer view and choose Export from the menu.
2. Click JAR file and click Next.

   

3. Click the checkbox to select the utility project that you wish to export. Use the Browse button to specify the location of the JAR file that will be created.

   

   If the file already exists, you may check the Overwrite existing files without warning selection to replace the existing file.

   Normally the Export source files option is unchecked. If you wish to include the Java source files in your archive, you must check this option. The most common reason to export an EAR file is to deploy for production, and in that case, the source files should not be included. Include the source files only if you wish to view/edit source at the destination.

   The screens that manage the JAR format are standard Eclipse screens documented in the Workbench User Guide.

4. Click Finish to create the JAR file.

How to Export an EJB Project to an EJB JAR

To export an EJB project to an EJB JAR file:

1. Right click anywhere on the Project Explorer view and choose Export from the menu.
2. Click EJB JAR file and click Next.

   

3. Use the pulldown to select the EJB project in the EJB module box. Use the Browse button to specify the location of the new EJB JAR file.

   

   If the file already exists, you must check the Overwrite existing file selection to replace the existing file.

   Normally the Export source files option is unchecked. If you wish to include the Java source files in your archive, you must check this option. The most common reason to export an EJB JAR file is to deploy for production, and in that case, the source files should not be included. Include the source files only if you wish to view/edit source at the destination.

4. Click Finish to create the EJB JAR file.

How to Export a Utility Project with Beehive Controls to a JAR

To export the controls in a utility project to a JAR file, follow the steps below. The resulting control JAR contains all of the contents of the utility project, but also stores the Beehive control manifest entries so that controls are displayed correctly in the IDE.

1. Right click anywhere on the Project Explorer view and choose Export from the menu.
2. Click Control JAR file and click Next.

   

3. Highlight the name of the utility project to use for the export. Use the Browse button to specify the location of the JAR file that will be generated.

   

   Normally the Include Java source files option is unchecked. If you wish to include the Java source files in your archive, you must check this option. The most common reason to export a JAR file is to deploy for production, and in that case, the source files should not be included. Include the source files only if you wish to view/edit source at the destination.

4. Click Finish to create the control JAR file.

 

Related Topics

none.