This is a feature of JBuilder Enterprise.
To display this dialog box, right-click an EJB module node in the project pane.
The Build page allows you to specify attributes about the JAR file that Making or Building the EJB module produces.
The Build page always contains an EJB page. If you have specified a target application server using Project|Project Properties and clicked Enterprise, using that page to select an application server other than Generic AppServer 1.0, the Build page will also have a second page that refers to your selected application server. For example, if you selected Borland Enterprise Server 5.0 as your application server, a Borland Enterprise Server 5.0 page appears on the Build page. Use an application-specific page such as the Borland Enterprise Server 5.0 page to specify options that are unique to the target application server.
The name of the JAR file that is produced when you choose to Make or Build the EJB module.
The name of the JAR file. JBuilder suggests a default name based on the name of the EJB module, but you can change it.
The path where the JAR file is created.
Lists the .xml
deployment descriptor files that are in the EJB module.
Use Add to add an existing deployment descriptor into the list of files in the EJB module.
Use Copy to copy the selected deployment descriptor to a new location.
Use Delete to remove the selected deployment descriptor from the list of files in the EJB module.
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.
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.
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.
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.
The title of this page is the name of the application server you have selected on the Enterprise 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, 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 is your target, the page includes these options:
Use these settings to determine how the JAVA2IIOP compiler behaves during a build.
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.
When selected, this option enables the generation of portable stubs, meaning stubs that contain code that is not specific to VisiBroker.
When selected, this option enables the generation of example implementation code.
When selected, this option enables the generation of _tie classes.
When selected, this option enables the generation of comments in the source code.
Enter any command-line options here. See the VisiBroker for Java Reference Guide for command-line options.
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.
Checking this option ensures that the EJB Designer's schema descriptor is included when the JAR file is built. The default value is unchecked.
Checking this option ensures that the EJB Designer's layout descriptor is included when the JAR file is built. The default value is unchecked.
If your selected application server is the Borland AppServer 4.5 application server (BAS), these are the options you see on the page:
Use these settings to determine how the JAVA2IIOP compiler behaves during a build.
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.
When selected, this option enables the generation of portable stubs, meaning stubs that contain code that is not specific to VisiBroker.
When selected, this option enables the generation of example implementation code.
When selected, this option enables the generation of _tie classes.
When selected, this option enables the generation of comments in the source code.
Enter any command-line options here. See the VisiBroker for Java Reference Guide for command-line options.
When selected, this option verifies during the build process that the enterprise beans in the JAR comply with the EJB 1.1 specification.
If your selected application server is a WebLogic application server, these are the options you see on the page:
These settings determine how the build is done.
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 setup a compiler for EJBC usage, choose Tools|Enterprise Setup, select the appropriate WebLogic page, and set the Compiler For EJBC Usage options.
Use this option to keep the source files for the generated stubs.
Enter any command-line options to pass to the EJBC compiler. Consult your WebLogic documentation for more information.
If your selected application server is the WebSphere 4.0 Advanced Edition or WebSphere Single Server 4.0, these are the options you see on the page:
The settings you specify here are passed to EjbDeploy.
Enter parameters you want passed to EjbDeploy.
From the drop-down list, select your database vendor.
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.
The top three radio buttons are file-specific options that control the currently selected file(s). These are the options:
The Copy and Do Not Copy options select an absolute behavior: always copy to the output path or never copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.
The third option, Use File Extension Defaults, allows JBuilder to decide whether to deploy the file based on its file extension in the file list below. This is the default behavior for all newly created files and files in existing projects. The correct extensions for the selected files are automatically selected in the list to highlight the default behavior.
Important: 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.
If you have changed the defaults for individual files and you want to return them to JBuilder's defaults, select the files again and choose Use File Extension Defaults.
Below the three file-specific options is a list of all known file extensions and their default deployment behavior. These defaults can now be changed on a project-by-project basis. Select one or more extensions and use the radio buttons on the right to change the default behavior for these extensions in the current project. These options include:
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.
Use this option to specify the content of your archive.
This option adds any classes that you have specifically added to your archive with the Add Class button. It also adds any classes that use one or more of the added classes.
This option also adds known resources. Known resources are those that you specifically add to the archive with the Add File button.
This option adds any classes that you have specifically added to your archive with the Add Class button. It also adds any classes that use one or more of the added classes.
It also adds all resources in the project's source path, such as images, video clips, sound files, etc.
This option gathers all classes on your project's outpath. The outpath is defined on the Paths page of the Project Properties dialog box. Usually, this is set to the classes
directory of your project.
It also gathers all resources on the project's source path, also set on the Paths page of the Properties dialog box. Usually, this is set to the src
directory of your project. Resources are files other than class files, such as images, video clips, sound files, and so on.
For all archive types, this option is on by default. This option is the safest, as it gathers:
The Add Class button displays the Select A Class dialog box, where you select a class to your archive. The class does not have to be in your project's outpath. If you choose either the Include Required Classes And Known Resources or the Include Required Classes And All Resources options, the Archive Builder will scan these added class files for additional class dependencies and will put those classes in the archive.
The Add File button displays the File Open dialog box, where you choose the file to add to your archive. The file must be in your project's source path. Use this option to add miscellaneous files in your archive, such as resources (.gif, .jpg, and audio files), property files, database drivers, or archived documentation (.html, readme.txt).
Note: The Add File dialog cannot look inside archive files. If a file or package you need is inside an archive file, extract it first to your source folder, then add it using the Add File button.
Removes the selected class or file from the list.
Use the Dependencies determine what to do with library dependencies. The libraries used in your project are listed, and you can choose an individual deployment strategy for each one.
Note: If you deploy any classes from the JDataStore package (com.borland.datastore
) or the VisiBroker package (com.visigenic
), you will see a warning reminding you that deploying these packages requires a separate deployment license. If you already have the appropriate license and don't want to see this warning again in this project, check "Don't warn me about this project again."
This is the default option for all archive types except applets. No libraries are included in your archive file. You need to distribute the redistributable libraries with your JAR file and include them on the CLASSPATH
at runtime, rather than putting the required classes from those libraries inside the JAR file. This is the easiest way to deploy and creates the smallest program JAR file.
If you choose this option, Exclude All
is displayed next to the selected library.
If you choose this option, the JBuilder attempts to determine which classes and resources are needed. It attempts to include any classes that are dependent on classes used in your project. It also attempts to include any resources that are used by any classes in your project. Note that this process won't work for many libraries.
If you choose this option, Include Deps
is displayed next to the selected library.
If you choose this option, the JBuilder attempts to determine which classes are needed by classes your project. It attempts to include any classes that are dependent on classes used in your project.
It will also gather all resources on the project's source path, set on the Paths page of the Project Properties dialog box. Usually, this is set to the src
directory of your project. Resources are files other than class files, such as images, video clips, sound files, etc. This option is useful if you are deploying third-party libraries.
If you choose this option, Deps & Resources
is displayed next to the selected library.
This option gathers all classes and resources, whether they are dependent on not. Everything, including libraries used by JBuilder's designers, is copied to your archive file. This option is the safest, but will result in a very large archive file.
If you choose this option, Include All
is displayed next to the selected library.
Use the deployment page to specify deployment options that are unique to your selected application server. If your selected application server is Generic AppServer 1.0, no deployment page exists.
The Deployment page displays a page for your selected application server. For example, if you specified Borland Enterprise Server 5.0 as your application server, the Deployment page displays a Borland Enterprise Server 5.0 page that you can use to specify options for deploying to the Borland Enterprise Server 5.0.
Use this page to specify parameters to send to the Java Virtual Machine.
Specify the host name.
Specify the parameters you want sent to the virtual machine.
Specify the container name.
Adds the project classpath to the classpath of the generated command line.
Consult your Borland Enterprise Server 5.0 documentation for information about parameters you can specify.
Use this page to specify parameters to send to the Java Virtual Machine.
Specify the host name.
Specify the container name.
Specify the parameters you want sent to the virtual machine.
Adds the project classpath to the classpath of the generated command line.
Consult your Borland AppServer 4.5 documentation for information about parameters you can specify.
Use this page to specify deployment options for WebLogic servers. Consult your WebLogic documentation for information about what to enter in these fields.
Specify a password.
Specify the unit name.
Specify options.
Specify parameters you want to pass to the virtual machine.
Adds the project classpath to the classpath of the generated command line.
Use this page to specify deployment options for WebSphere Application Server 3.5. Consult your WebSphere documentation for information about what to enter in these fields.
The name of the primary node.
The name of the application server.
The container name.
Specify parameters sent to the virtual machine.
Generates an XML file for input to the XMLConfig utility. Check this check box when you want to generate the XML file and then modify it. When generated, the file appears under the EJB module node in the project pane. If you then want to test your modifications, you should then uncheck this option so that the XML file is not overwritten.
Adds the project classpath to the classpath of the generated command line.
Use this page to specify deployment options for WebSphere Application Server 3.5. Consult your WebSphere documentation for information about what to enter in these fields.
Specify the types running in the container you want to see listed.
Specify deployment options.
The parameters to pass to the VM.
Use this page to specify deployment options for the iPlanet Application Server 6.0. Consult your iPlanet documentation for information about what to enter in these fields.
Specifies that the module deploys to a local server.
Specifies that the module deploys to a remote host. You must specify the following settings.
The name of the host or the IP address.
The port used to communicate with the host.
Enter a user name to connect with the host.
Enter a password to connect with the host.
Checking this option does nothing.