Build page (EJB Module Properties dialog box)

The Build page allows you to specify attributes about the JAR file that Making or Building the EJB module produces.

To display the Build page, right-click an EJB module node in the project pane and click the Build page in the Properties dialog box that appears.

The Build page always contains an EJB page. If you have specified a target application server by choosing Project|Project Properties and clicking the Server page you may have a second page that refers to your selected application server. For example, if you selected Borland Enterprise Server 5.0.2+ as your application server, a Borland Enterprise Server 5.0.2+ page appears on the Build page. Use an application-specific page such as the Borland Enterprise Server 5.0.2+ page to specify options that are unique to the target application server.

The Build page also contains a Resource page.

EJB page

Output JAR File

The name of the JAR file that is produced when you choose to Make or Build the EJB module.

Name

The name of the JAR file. JBuilder suggests a default name based on the name of the EJB module, but you can change it.

Path

The path where the JAR file is created.

Deployment Descriptors In Module

Lists the .xml deployment descriptor files that are in the EJB module.

Add button

Use Add to add an existing deployment descriptor into the list of files in the EJB module.

Copy button

Use Copy to copy the selected deployment descriptor to a new location.

Delete button

Use Delete to remove the selected deployment descriptor from the list of files in the EJB module.

Include Deployment Descriptors In Output JAR File

Determines whether the deployment descriptors are included in the JAR file. By default, this option is checked. If you don't want to use JBuilder's Deployment Descriptor editor to edit the deployment descriptors, but want to use another tool to edit the deployment descriptors, uncheck the Include Deployment Descriptors in Output Jar File option. The JAR file that is created won't include the deployment descriptors in it.

Additional Files For JAR META-INF

Lists any additional files you want added to the META-INF directory of the JAR file. To add an additional file, click the Add Button and specify the location of the file. You'll need to do this if you've added a new class, for example, to your project and you want it become part of the JAR file.

Automatic Copy Of Descriptors On Save

Copy Descriptors

When checked, a copy of the deployment descriptors are copied to the specified directory whenever you save the EJB module.

Directory

The directory where a copies of the deployment descriptors are saved.

Remove Stub Files On Application Server Change

When this option is selected, any generated stub files are deleted when you select a new target application server. This prevents the stubs meant for another application server from being copied into the new generated JAR file.

Always Create JAR When Building The Project

By default, a JAR file is always created during the build process. Uncheck this option if you want to defer creating a JAR file until you're ready to begin testing.

Borland Enterprise Server 5.0.2+ page

The title of this page is the name of the configured application server you have selected on the Server page of the Project|Project Properties dialog box. If you select a different application server, a page with the name of the new application server on its tab appears here instead.

Options available on this page vary, depending if your selected application server is the Borland Enterprise Server 5.0.2+, the Borland AppServer 4.5, a WebLogic 5.1 or 6.x+ application server, a WebSphere 3.5 or 4.0 application server. If Borland Enterprise Server 5.0.2+ is your target, the page includes these options:

JAVA2IIOP Settings

Use these settings to determine how the JAVA2IIOP compiler behaves during a build.

Generate Stubs For Home Interfaces

Check this option when you want to generate IIOP-compliant stubs for the home interfaces of the beans in this EJB module. When this option is checked, the other JAVA2IIOP options are enabled. If this option is unchecked, the other options are disabled.

Strict Portable Code Generation

When selected, this option enables the generation of portable stubs, meaning stubs that contain code that is not specific to VisiBroker.

Generate Example Implementation

When selected, this option enables the generation of example implementation code.

Generate Tie Bindings

When selected, this option enables the generation of _tie classes.

Generate Comments

When selected, this option enables the generation of comments in the source code.

Options

Enter any command-line options here. See the VisiBroker for Java Reference Guide for command-line options.

Verify Compliance After Building JAR

When selected, this option verifies during the build process that the enterprise beans in the JAR comply with the EJB 1.1 or 2.0 specification.

Include EJB Designer Schema Descriptor In Output JAR file

Checking this option ensures that the EJB Designer's schema descriptor is included when the JAR file is built. The default value is unchecked.

Include EJB Designer Layout Descriptor in Output JAR file

Checking this option ensures that the EJB Designer's layout descriptor is included when the JAR file is built. The default value is unchecked.

BAS 4.5 page

If your selected application server is the Borland AppServer 4.5 application server (BAS), these are the options you see on the page:

JAVA2IIOP Settings

Use these settings to determine how the JAVA2IIOP compiler behaves during a build.

Generate Stubs For Home Interfaces

Check this option when you want to generate IIOP-compliant stubs for the home interfaces of the beans in this EJB module. When this option is checked, the other JAVA2IIOP options are enabled. If this option is unchecked, the other options are disabled.

Strict Portable Code Generation

When selected, this option enables the generation of portable stubs, meaning stubs that contain code that is not specific to VisiBroker.

Generate Example Implementation

When selected, this option enables the generation of example implementation code.

Generate Tie Bindings

When selected, this option enables the generation of _tie classes.

Generate Comments

When selected, this option enables the generation of comments in the source code.

Options

Enter any command-line options here. See the VisiBroker for Java Reference Guide for command-line options.

Verify Compliance After Building JAR

When selected, this option verifies during the build process that the enterprise beans in the JAR comply with the EJB 1.1 specification.

WebLogic 5.1 or WebLogic 6.x+ page

If your selected application server is a WebLogic application server, these are the options you see on the page:

EJBC Settings

These settings determine how the build is done.

Use EJBC To Generate Stub Files

Check this option when you want to use the EJBC compiler to generate stub files. If this option is checked, the other EJBC options are enabled; otherwise they are disabled.

To set up a compiler for EJBC usage, choose Configure Servers dialog box, select either WebLogic Application Server 5.1 or WebLogic Application Server 6.x+ from the list of servers, click the Custom tab, and set the Java Compiler For EJBC Usage options.

Keep Generated Stub File Source

Use this option to keep the source files for the generated stubs.

Remove Project Output Path From Classpath

Use this option to remove the project output path from the classpath.

Warn When Spaces In Classpath

Select this option when you want to receive a warning message when spaces are in the classpath. The EJBC compiler won't accept spaces in the classpath.

Display All Output

Select this option when you want to see all the output the EJBC compiler can generate.

Options

Enter any command-line options to pass to the EJBC compiler. Consult your WebLogic documentation for more information.

WebSphere AE 4.0

If your selected application server is the WebSphere 4.0 Advanced Edition, these are the options you see on the page:

EjbDeploy Settings

These settings are used by the EjbDeploy utility.

Options

Specify options you want passed to the EjbDeploy utility.

Database Vendor

Select your database vendor and version from the drop-down list.

CMP Descriptors

These options determine whether JBuilder generates the CMP deployment descriptors and, if so, how they are generated.

Generate CMP Descriptors

Check this option if you want JBuilder to generate CMP deployment descriptors for entity beans that target WebSphere. If this option is unchecked, the default value, the EjbDeploy utility will build the files, but you will lose all the mapping information you added using the EJB 1.1 EntityBean Modeler wizard.

Even if you choose to have JBuilder generate CMP deployment descriptors, JBuilder might not be able to do so. JBuilder attempts to use column types that are actually referenced by the WebSphere mapping files. Frequently there may not be a direct mapping. You will know this if you have checked the Generate CMP Descriptors check box and clicked OK to close the dialog box and you see an exception that begins with text like this in JBuilder's console window (you will have console window if you started JBuilder using JBuilder.exe, not JBuilderw.exe):

java.lang.Exception: Could not find primitive type reference for <type name> in <database map file>

This message indicates that JBuilder couldn't find a reference for the <type name> in the described file. Use the Data Type Substitutions In Generated Descriptors option to correct the problem.

Database Mapping Files

This option is enabled when the Generate CMP Descriptors option is checked. The Database Mapping Files table displays a list of database types and versions. For each database type, the corresponding primitives map file and the Java type map file are shown.

You can change the mapping files used by a database. Click the Add button to add a new row to the table. Specify the Database Type and fill in the name of the Primitives Map File and the name of the Java Type Map File you want used.

To delete a database mapping, select the row in the table and choose Remove.

Data Type Substitutions In Generated Descriptors

Use this option when you have checked the Generate CMP Descriptors check box but JBuilder is unable to generate the descriptors without throwing an exception. See the Generate CMP Descriptors option for more information.

When JBuilder can't generate the CMP desciptors, open the database map file that is causing the problem and look for a type that you think comes closest to the type that can't be found. Click the Add button next to the Database Type Substitution In Generated Descriptors table and add a new item for your database type. The Original Type is the type that can't be found and the Substitute Type is the type you want to try to substitute. After you click OK to save your changes and close the dialog box, the next time JBuilder attempts to rebuild the custom descriptors (when you modify the beans or when you recheck the Generate CMP Descriptors check box and choose OK to close the dialog box), it uses your substitue type.

You may notice that Borland has already added some needed type substitutions to the table.

To remove a substitution, select the row in the table and choose Remove.

WebSphere 4.0 AES

If your selected application server is the WebSphere 4.0 Single Server, these are the options you see on the page:

Use this page to specify deployment options for WebSphere Application Server Single Server Edition, Version 4.0. Consult your WebSphere documentation for information about what to enter in these fields.

EjbDeploy Settings

These settings are used by the EjbDeploy utility.

Options

Specify options you want passed to the EjbDeploy utility.

Database Vendor

Select your database vendor and version from the drop-down list.

iPlanet 6.x+

Resource page

JBuilder copies all known resource types from the source path to the output path during the compile process. By default, JBuilder recognizes all images, sound, and properties files as resources and copies them to the output path. You can override these default resource definitions on individual files or by file extension project wide. See "Setting the output path" for more information on the output path.

On the Build page of the Properties dialog box you can set individual files as resources, as well as set project-wide resources by file extension.

You can access the Resource tab on the Build page two ways:

There are two groups of radio buttons that have different results:

Copy

Copies selected file(s) to the output path. The Copy option selects an absolute behavior: always copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.

If you changed the defaults for individual files and you want to return them to the project defaults as specified in the Project-wide Defaults By Extension list, select the files again and choose Use File Extension Defaults.

If the selected files or extensions do not all share the same setting, none of the radio buttons in the corresponding group are selected. Selecting one of the radio buttons changes everything to the same value, while leaving none selected allows the differing values to be left alone.

Do Not Copy

Does not copy the selected file(s) to the output path. The Do Not Copy option selects an absolute behavior: never copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.

If you changed the defaults for individual files and you want to return them to the project defaults as specified in the Project-wide Defaults By Extension list, select the files again and choose Use File Extension Defaults.

If the selected files or extensions do not all share the same setting, none of the radio buttons in the corresponding group are selected. Selecting one of the radio buttons changes everything to the same value, while leaving none selected allows the differing values to be left alone.

Use File Extension Defaults

Copies all files based on their file extension to the output path that are labeled Copy in the Project-wide Defaults By Extension list. File types that are labeled Do Not Copy are never copied to the output path on compilation. This is the default behavior for all newly created files and files in the current project. The correct extensions for the files currently selected in the project pane are automatically selected in the list to highlight the default behavior. The default settings for the project can be changed in the Project-wide Defaults By Extension section.

Project-wide Defaults By Extension

These options are project wide and control what is copied to the output path by file extension. Select a file type in the Project-wide Defaults By Extension list and choose Copy or Do Not Copy. For example, if html is changed from Do Not Copy to Copy in the Project-wide Defaults By Extension list, then all HTML files in the project are copied to the output path during compilation.

Copy

Copies all files of the selected type to the output path.

Do Not Copy

Does not copy any files of the selected type to the output path.

Reset

Use the Reset button to return all files in the file extension list to the state they were in when the dialog box was displayed. Remember, this does not change your individual file settings to the default.