Borland JBuilder 7 Update 003
Release Notes

Installation Instructions

Important!  Do not apply this patch to the JBuilder 7 WebLogic Edition. That edition already contains the fixes included in this patch.

Read all the instructions through once before applying the update. The following description assumes that JBuilder has been installed in the directory \jbuilder7. If you have installed JBuilder 7 in a different directory, substitute the one that you used. Unix users should substitute a simple (forward) slash ("/") wherever a backslash ("\") appears in a path name.

This patch is delivered as one ZIP file and Release Notes.

To install the patch:

1. Shutdown JBuilder 7.
2. Copy the patch ZIP file to a local directory.
3. Unpack the ZIP file from the root of the JBuilder 7 installation. This should extract jb7_all.jar and jb7_build_001.jar into the JB_HOME\patch directory, and navigator.jar into the JB_HOME\lib\bes directory.

You can use WinZip or a similar utility to unarchive the files from the ZIP file. Make certain that you preserve the directory or folder names when you unarchive the files. You can also use the JAR tool to unarchive the files:

1. At the command line, change directories to the directory where you installed JBuilder 7 (example: cd \JBuilder7).
2. <JDK_HOME>/bin/jar -xvf jb7_patch_003.zip (where <JDK_HOME> is the directory where your JDK is installed).

Borland Enterprise Server users only

1. Download the latest version of the Borland Enterprise Server 5.0.2 patch and install it in the <BES_home>\lib\patches directory.
2. Reconfigure your server in JBuilder:
1. Choose Tools|Configure Servers. Select "Borland Enterprise Server 5.0.2+" from the list, then click "Reset to defaults" on the right.
2. Click OK in the 'Configure Servers' dialog box.
3. Click OK in the "Some changes have been made that will only take effect after JBuilder has been restarted" message dialog.
4. Choose Tools|Configure Servers. Enable the server configuration for Borland Enterprise Server 5.0.2+. Set the home directory.
5. Click OK in the 'Configure Servers' dialog box.
6. Click OK in the "Some changes have been made that will only take effect after JBuilder has been restarted" message dialog.
7. Restart JBuilder.

1. Choose Project|Project Properties. Click on the Server tab.
2. Click the ellipsis (...) button next to "Single server for all services".
3. Click OK in the Configure Servers dialog box. Ensure that "Borland Enterprise Server 5.0.2+" is selected in the list.

• -Daxis.enableListQuery=true
• -Dlog4j.configuration=file:///<JB_HOME>/defaults/log4j.properties

General fixes

• [136227] Fixes IllegalStateException in JBuilder (which doesn't allow JBuilder to shut down properly), that occurs after editing a field in the Configure Servers dialog box, then pressing Enter to close the dialog box.
• [137811] Code Templates can now be edited, added, or deleted in JBuilder SE.
• The ability to import WebGain Visual Cafe projects has been enhanced to also include web applications.
• [137484] Fixes "-build option does not work in SE."
• [140776] Fixes "Use of Edit|Undo menu, after an extract method, causes instability in the refactoring engine."
• [140778] Fixes "After refactoring, new resulting method is incorrect. Method returns void."
• [143580] The Add, Edit, Delete buttons for code templates are now enabled in JBuilder SE. The templates defined can be used in the editor.
• [143633] Editing a code template no longer causes it to be deleted.

Improved BES support

• [134750] When you run or debug a Borland Enterprise Server instance in JBuilder, as part of the "pre-run" tasks, if a management agent is not detected as running, JBuilder will attempt to start the management agent automatically. The following system properties associated with this task can be set as VM parameters in jbuilder.config using the vmparam directive:
• -DBES50xAutoAgentStartup=<true|false>

This is a reverse property -- i.e. if it is not set, JBuilder will attempt to automatically start the management agent. If set to "false" or "FALSE", the agent will not be automatically started.
• -DBES50xAgentStartupTimeout

This property indicates the amount of time in milliseconds that JBuilder will wait for the server to come up before starting the partition. The default value is 30000 ms.
• [134859] Shutting down the Borland Enterprise Server Management Agent terminates all processes (including any osagent processes). An activity monitor is now displayed during the shutdown process. Shutdown now includes a timeout which takes effect if the the server process does not terminate. At this point, JBuilder will terminate the server process. This timeout can be set using the VM parameter BES50xAgentShutdownTimeout. To set this parameter, edit the jbuilder.config file in your JBUILDER_HOME/bin directory and add the directive, vmparam -DBES50xAgentShutdownTimeout=<timeout period in milliseconds>. The default value is 90000 ms.
• [135494] By default, the server run configuration property, "Remove archives already deployed to server" checkbox (on the Server Run Configuration property page when the Archives node is selected) is now true.
• [135495] Deployment functions (deploy/redeploy/undeploy) will not restart partitions when run from within JBuilder. Partitions run within JBuilder can now be managed using the Borland Enterprise Server console. To enable this feature, the Borland Enterprise Server patch must be installed on the server.
• [136273] A server can now be debugged with the JSP/Servlet service turned off.
• The following Borland Enterprise Server services are now turned off by default to speed up partition startup time:
• JDataStore
• Connector (visinaming)
To enable these services, select Project|Project Properties, Servers tab, thenselect the services from the service tree on the left.

Partition classloader policy should preferrably not be changed from the default ('per_module'). To use partitions with the 'per_module' classloader setting in JBuilder,

1. Package existing EJB and web applications in a EAR module for deployment.
2. Load EJB JARs and WARs in separate partitions.
1. Create a server run configuration for the first partition (to load EJB jars).
2. Edit the run configuration and click on the 'Archives' node. Select all EJB jars from the list and deselect any web applications (WARs) or enterprise archives (EARs).
3. Deselect the JSP/Servlet service in the Services list.
4. Create a server run configuration for the second partition (to load WARs).
5. Edit the run configuration and click on the 'Archives' node. Select all web applications (WARs) from the list and deselect any EJB JARs or enterprise archives (EARs).
6. Deselect the EJB and the Naming services in the Services list.
7. Start the management agent by choosing Tools|Borland Enterprise Server Management Agent.
8. Start the EJB partition and then the web partition.
Note: There should be only one naming service started. The naming service should be enabled on the EJB partition. The order of startup is important as the partition with the naming service should be started first.
• [141016] The security parameter (-Dvbroker.security.disable) is no longer set when starting the management agent or the partition. This parameter will now only be used for internal communication with the Borland Enterprise Server Management Agent (partition startup/stop, deployment, management agent shutdown). To configure this setting in JBuilder:
1. Choose Tools|Configure Servers.
2. Select "Borland Enterprise Server 5.0.2+", then click on the 'Custom' tab.
3. Click on Advanced Settings, then change the value of the "Use security" option. By default, this is always turned on.
It is useful to change this setting, if management agent security on the server side is turned off manually. Ensure that this setting always matches the security setting for the management agent on the server side. Refer to Borland Enterprise Server documentation for further information. Internal communication with the management agent in JBuilder will not work if these settings do not match.

Support for JBuilder Personal and MobileSet 3

• [136736] When Auto Discovery is turned off, an application will now make when the build configuration that is set to make is run from toolbar, F9, or Project menu.
• [136549] When the JDK is configured for J2ME, users can switch the configuration to another JDK.

File List