Borland JBuilder 2006

Introduction

This document contains a subset of known problems, workarounds and tips for JBuilder 2006.

Refer to the New Features Guide for information about JBuilder 2006. The New Features Guide describes all of the new features and updates in this release and supercedes information in the earlier books.

Note: The complete documentation set was not updated for this release.

Table of Contents

System Requirements
CaliberRM Updates
Peer to Peer Collaboration Updates
Known Issues

• General
• Optimizeit Tools
• Web Services
• Enterprise JavaBeans (EJB)
• Web Development
• Team Development
• Mobile Development
• XML
• Debugger
• Designer
• OpenTools
• Borland Enterprise Server
• JDataStore
• Sun Java System Application Server
• JBoss
• WebLogic
• Unix
• Samples
• Performance
• International
• Documentation

Getting Help
Installation

[ top ]

System Requirements

The system requirements for each of the Borland JBuilder editions are listed below:

Borland® JBuilder® 2006 Enterprise

• 512 MB RAM recommended minimum
• 768 MB RAM recommended
• 650 MB hard disk space plus additional space for development files and temporary space during installation
• CD-ROM drive
• High-resolution monitor (1024x768 or higher, 256 colors)
• Mouse or other pointing device

Windows®

• Intel® Pentium® III/800 MHz or higher (or compatible)
• Microsoft® Windows® 2000 (SP4), Windows XP (SP2), or Windows 2003

Linux®

• Intel Pentium III/800 MHz or higher (or compatible)
• Red Hat® Enterprise Linux 3.0
• Novel SuSE Enterprise Linux 9

Solaris^TM

• UltraSPARC^TM II or higher
• Solaris^TM 9 (2.9) and 10

JBuilder®2006 Developer

• 256 MB RAM recommended minimum
• 512 MB RAM recommended
• 570 MB hard disk space plus additional space for development files and temporary space during installation
• CD-ROM drive
• High-resolution monitor (1024x768 or higher, 256 colors)
• Mouse or other pointing device

Windows®

• Intel® Pentium® III/500 MHz or higher (or compatible)
• Microsoft® Windows® 2000 (SP4), Windows XP, or Windows 2003

Linux®

• Intel Pentium III/500 MHz or higher (or compatible)
• Red Hat® Enterprise Linux 3.0
• Novel SuSE Enterprise Linux 9

Solaris^TM

• UltraSPARC^TM II or higher
• Solaris^TM 9 (2.9) and 10

[ top ]

CaliberRM Updates

CaliberRM is not currently available in this release of JBuilder. You can get the CaliberRM plug-in from the Borland website (www.borland.com/downloads/registered/download_jbuilder.html) when it becomes available.

[ top ]

Peer to Peer Collaboration Updates

JBuilder 2006 contains support for Google^TM Talk which is based on the Jabber/XMPP protocol. To use, enter talk.google.com for the server and 5222 for the port. Then go to the Client page under Jabber and enter your full Gmail address (e.g. myAccount@gmail.com) as the account name.

At this time the current beta of Google^TM Talk does not support server-to-server functionality. This means that Jabber and Gmail accounts are currently not interchangeable. If you put a jabber.org contact in your Gmail contact group, Gmail will not be able to report when that person is online. This prevents you from initiating a chat with the jabber.org contact.

[ top ]

Known Issues

These issues are organized by product area.

General

For updates and service packs for the Java Development Kit (JDK), see: http://java.sun.com/j2se/.

The Quality Central plugin is not available for this release of JBuilder. See http://qc.borland.com.

[229541] If you receive an error when you run or debug a project with JDK 1.4, change the default project properties Target VM from JDK 5 to 1.4 (Project Properties|Build|Java).

[229774] If you experience problems reading Sun's JDK documentation in the help viewer, open the HTML files in another browser, such as Internet Explorer.

Troubleshooting Running JBuilder

JBuilder hangs on startup or locks up at the splash screen

There are several possible causes for this problem. The most common are related to issues with your graphics driver.

To troubleshoot installation graphics driver issues, try the following:

• First, visit the website of the manufacturer of the graphics card to download and install the latest driver.
• Windows 2000/XP: If the issue is not resolved, try turning down the graphics card acceleration. To do this:
  1. Right-click on the desktop.
  2. Choose Properties|Settings|Advanced|Troubleshoot.
  3. Set the Hardware acceleration to None.
  4. Start the JBuilder installation program again.
• Try reducing the resolution and/or color depth. Many high-end graphics adapters have high-resolution modes that can cause some aspects of Java to experience difficulties.
• With certain video adapters you may experience some screen painting problems or crashes when running JBuilder. If this happens, try to uncomment a couple of lines in your /JBuilder2006/bin/jdk.config file:

  vmparam -Dsun.java2d.ddoffscreen=false
  #vmparam -Dsun.java2d.noddraw
  #vmparam -Dsun.java2d.d3d=false
  

  To uncomment the setting, remove the # symbol preceding the lines and try to run JBuilder again to see if the behavior improves.

If this fails to correct the problem, try one of the other troubleshooting suggestions described in the following sections.

JBuilder throws java.lang.NoClassDefFoundException or java.lang.Object for java.lang.NoSuchMethodError

This behavior might occur if a third-party JAR was placed in your JBuilder2006\lib or JBuilder2006\jdk\lib directory. Third-party JAR files should be placed in your JBuilder2006\lib\ext directory. There is only one sure way to resolve a corrupted JDK installation: Uninstall and then reinstall your JBuilder product. Make sure that you manually delete any residual files left over before you re-install JBuilder.

Exceptions are reported related to a third-party OpenTool

JBuilder has a plug-in mechanism, and the plug-ins that you can add to JBuilder are called OpenTools. There are a number of third-party OpenTools that typically come in the form of a JAR file and usually get installed to your JBuilder2006\lib\ext directory. Some OpenTools have been written for older versions of JBuilder and can cause your current version of JBuilder to fail to start. If you are having trouble getting JBuilder to launch, remove any OpenTools and re-start JBuilder.

JBuilder does not start or behaves strangely

There are some rare times that some unexplainable behaviors occur in JBuilder or it inexplicably will not start when it was working fine previously. One possible fix is to clear out your existing user settings so that new default ones will be used. To do this, delete the .jbuilder2006 and .primetime2006 directories in your "user home" directory. New default ones will be created the next time you launch JBuilder.

Warning: You should make a backup copy of these directories in case you want to borrow some of your previous settings, as you will lose all of them by performing this fix.

JBuilder runs slowly or is not painting correctly

Most painting problems are the results of issues with your graphics driver. See the section "JBuilder hangs on startup or locks up at the splash screen" for information on troubleshooting graphics-related issues.

If you are receiving out of memory error messages or exceptions, you need to increase the amount of available memory. You can do this by modifying the value of the vmmemmax setting in the jbuilder.config file (located in your JBuilder2006\bin directory). (See the "JBuilder Configuration README" for additional information on setting JBuilder options.) Although JBuilder has minimum and preferred memory specifications listed you need to take into account that your operating system, other applications, and the application that you are developing take memory as well. The simple solution is to add more physical RAM to your machine.

Tips

• When "Synchronize Output Dir" is turned on (Project Properties|Build|Java), all of the class files in the output path directory that do not have source files are deleted during compilation. This is the default setting. You should turn this off when you manually add classes to the output directory.
• [204604] To invoke code audits, choose Warnings in the structure pane, or choose Code Audits in the project properties dialog box.
• [220801] You can now set additional options for some audits in the Code Audits page in the project properties dialog box. If the audit has additional options available, they display in the dialog box when that audit is selected.

Using JBuilder 2006 with other versions of JBuilder

Use the Import Settings wizard (Tools|Import Settings) to import settings from older releases. The wizard automatically runs the first time you launch JBuilder 2006 if a previous installation is found. Or, redefine these configurations by choosing Enterprise|Configure Servers or Enterprise|Enterprise Setup|Database Drivers.

You can change the location where JBuilder looks for your .jbuildern directory by adding the following entry to the jbuilder.config file:

vmparam -Djbuilder.home=path to the parent directory for .jbuilder-dir

where .jbuilder-dir is the name of your alternate home directory.

Note: Do not place quotation marks around the values you add to your jbuilder.config file, even if they contain spaces. Doing so will generate a parsing error.

Known Problems

• [209134] The VFS cache does not always appear to be cleared when a project is made. If a project is in a project group, this means that dependent projects in the group will not have the correct information.
• [205674] SQLJ files will not build if the path to the JDK contains spaces, or if the name of the project file contains a space in it.
  Workaround: Install the JDK to a directory that does not contain spaces. Do not use spaces in the name of your project files.
• [186076] If a user has moved the main class to a different package (especially through refactoring), any existing run configurations utilizing the class are no longer valid. It is not obvious to the user that the configuration is not valid.
• [166857] Making a class that is dependent on another class results in a cannot resolve symbol error.
• [228612] The Find/Replace Text dialog box Ignore Comments option has no effect when you close the dialog by selecting Find All.

[ top ]

Optimizeit Tools

Optimizeit includes a Troubleshooting Guide that answers frequently asked questions about Optimizeit installation and configuration. These are some additional issues not covered in the Troubleshooting Guide. They are sorted by platform and JDK.

Documentation notes: Although JBuilder Developer includes only Optimizeit Profiler (not the whole suite of tools), it includes the Optimizeit documentation for the entire suite.
Many procedures describe how to use the standalone Optimizeit tools.

JDK Issues:

• Make sure you are using the version of the JDK installed with JBuilder. Some Optimizeit functions will not operate properly unless you are running the correct version.
• [184026] The JDK 1.4.1 heap dump facility is unstable. If you get a crash in the Instance Display (Reference Graph) mode or Memory Leak Detector, try switching to JDK 1.4.0 or JDK 1.4.2.
• [182501] When you profile applications using IBM JDK 1.4, some Abnormal Container Growth errors are not reported by the Application Quality Analyzer.
• [149715] When testing an application using the IBM JDK 1.3 with Code Coverage, the test may return an OutOfMemory exception. This problem can be fixed by either specifying the Java parameter -Dccoverage.classpath= to the java invocation, or by increasing the minimum heap size to a bigger value using the -Xms256M startup command parameter (where 256 is an example of the minimum size, in megabytes).
• [149433] IBM JDK 1.3.1 crashes when the Optimizeit Profiler requests a JVMPI heap dump. For example, this could happen if you select a class in the Heap view and click on Instance view. This problem does not occur with IBM JDK 1.3.
• [163814] When testing applets with Optimizeit, you must use JDK 1.4 and above if your class names include high ASCII characters. Testing with JDK 1.3.1 or older is not possible because the oldjava command does not recognize high ASCII characters in a class name.

Windows Issues:

• On Windows machines, you may get better performance if you disable the Windows default indexing program, findfast.exe. This program can be manually disabled from your control panel.
• On Windows machines, Hotspot is not the default virtual machine setting for JDK 1.3.1; to use Hotspot with this JDK, you must open the Virtual Machines tab on the Settings dialog box and select the Hotspot option.

Solaris and Linux Issues:

• [230454] On Linux, when exporting data from Optimizeit, the Browse button used to specify the export destination does not work. You must type the destination filename or use the default filename.
• [221195] On Solaris, snapshots generated by Unit Test profiling contain performance data from classes that are not part of the test case or test suite.
• [182735] On Solaris, early classes cannot be instrumented with JDK 1.4.x. This means that some errors, such as container growth errors, cannot be generated.
• On Solaris machines, some windows have clipped text because the font is too large. Lower your font size and refresh the screen to see all the information.
• [149121] On UNIX, by default some virtual machines (such as JDK 1.2.2) use green threads, but Thread Debugger does not support green threads. If you are using green threads, Thread Debugger will not be able to launch the Java program. Before running your test program, make sure the virtual machine is using native threads by setting the environment variable THREADS_FLAG to native. If native threads are not available on your JVM (for example, 1.3.0 or 1.3.1. JDK classic runtime for Linux) then you must install another virtual machine. If you must use JDK 1.3.0, the Blackdown version has a native implementation. See the Troubleshooting Guide for more information on selecting native or green threads.

  Note: Blackdown JDKs are not supported for this version of Optimizeit Enterprise Suite.

• [149782] On Linux machines, the IBM JDK 1.2.2 will not start testing when the test is begun from within the Optimizeit UI; this is true for all three Optimizeit tools. This is because of the way native threads are used in the virtual machine. If you need to start a test from within Optimizeit (specifying the test parameters on the Settings dialog box and clicking Start Now) you must use a different JDK.

  Note: IBM JDK 1.2.2 is not supported for this version of Optimizeit Enterprise Suite.

• [198456] On Solaris, when using Thread Debugger with JDK 1.3 and 1.4, you may have to specify the -Xint option. This option sets the VM to interpreted mode, disabling the JIT. If JIT is enabled, a bug in JVMPI causes Optimizeit Thread Debugger to become unstable when a MONITOR CONTENDED EXIT event occurs.

[ top ]

Web Services

Known Problems

• [225696] JBoss J2EE 1.3 web services (java/EJB): Generated stubs do not compile.
  Workaround: Move the Axis library to the top of the list of required libraries.
• [222180] When using JBoss 4.0, WSDL links for 1.4 Java and EJB Web Service from the available services list are incorrect.
  The correct link for EJB WSDL is: http://localhost:8080/EJBModule1/Enterprise1Service?WSDL from the link in the list of deployed services. And the correct link for Java WSDL is: http://localhost:8080/WebModule1/Bean1Interface1?WSDL.
• [208538] In order to build successfully when using the WebLogic toolkit with Export to Ant, you need to uncheck "Use Borland Java Compiler" in the build.xml properties Ant page.
• [225866] Export to Ant fails for 1.3 java service with Axis Toolkit.
  Workaround: Make a new library that includes JB/lib/jb-axis-ant.jar, and added it to "Libraries containing custom ant tasks" in Project properties|Build|Ant.
• [207835] The WS-I shell scripts need to be modified in order to run the WS-I Analyzer and Monitor inside JBuilder on Unix platforms.
  Workaround on Linux:

  Enter the following commands at the command prompt:

  cd /tools/ws-test-tools/java/bin
  dos2unix Analyzer.sh
  dos2unix Monitor.sh
  chmod +r+x  Analyzer.sh Monitor.sh
  

  
  Workaround on Solaris:
  Enter the following commands at the command prompt:

  cd /tools/ws-test-tools/java/bin 
  dos2unix Monitor.sh temp.sh
  mv temp.sh Monitor.sh 
  dos2unix Analyzer.sh temp.sh
  mv temp.sh Analyzer.sh
  chmod +r+x  Analyzer.sh Monitor.sh 
  

• [207018] When using WebLogic 8.1 and 7.x with the Axis toolkit, running generated test cases fails.
  Workaround: Move the Axis library to the top of the list in the required libraries for your project and run the test case again.
• [186402] WebLogic 7: Building an application module with a web services web module and a non-webservices web module does not include the non-webservices web module in the EAR.
  Workaround:
  1. Open the web services designer and click on the Module settings button in the toolbar and select the option "Use saved designer output".
  2. Expand the web services designer node and open build_WebLogic.xml.
  3. Locate the task "JBServicegenTask" and modify the servicegen element by adding the following attribute:

     overwrite="false"
     

  4. Rebuild the application module.
• [227486] Web services designer (J2EE 1.3) in the Server inspector, Server Options page, the field Soap Version is now named Type Mapping Version.

[ top ]

Enterprise JavaBeans (EJB)

Known problems

• [227778] Rebuild project fails after change session bean name in EJB Designer since the change is not updated to mapping file and webservices.xml.
  Workaround: As soon as the bean name is changed the model is out of sync. If you switch to the 1.4 designer tab you'll see the Error insight icon appear. Open and close the service bean inspector in the web service designer (by clicking on the display name) to fix the error. Rebuild now should work fine.
• [225742] When you expose a java bean as web service (1.3) and click Validate local installation's configuration, you will see the following error. Error: could not find class org.apache.log4j.Layout from file log4j-1.2.8.jar Axis may not work.
  Workaround: Add log4j-1.2.8.jar to the required libraries in the project properties. Each server provides it's own log4j-1.2.8.lib.
• [209419] To run a CORBA application, the following VM parameters need to be added to the application's run configuration:

  -Dvbroker.agent.port=<smart agent port> 
  -Dborland.enterprise.licenseDir=<USER_HOME> 
  -Dborland.enterprise.licenseDefaultDir=<BES_install>/license
  

  where USER_HOME is the default location of the Borland license directory (.borland). If this is different from the default license directory, replace it with the directory where Borland license information is stored.
• [209361] Linux only: Borland Enterprise Server is currently not supported for the Sun Java Desktop System platform.
• [201628] Redeploying a DAR causes the datasource objects contained in it to be re-registered in the JNDI tree. However, this does not imply that any JDBC pools instantiated in the partition using the earlier datasource data automatically gets refreshed with the new datasource information (e.g. if the previous datasource pointed to DB1 and the refreshed DAR points to DB2 then JNDI is updated but the JDBC pool still points to DB1).
• [203532] Trying to bring up the BES console with more than one version of the BES server configured in JBuilder throws a ClassCastException
  Workaround: Configure JBuilder to use only a single version of the server at a time.
• [202084] Borland Enterprise Server (6.0 and 6.5) users using JDataStore and creating databases using the JDataStore tools shipped with JBuilder should create their datastores in JDS 6 format. Do not choose to copy over any JDataStore libraries from JBuilder (Run|Configurations. Server run configuration. Libraries) when starting up the server in JBuilder.
• [184164] Including a library as a dependency for a module does not include JARs in the library which are shared in the client library.
• [171998] Creating a module from a directory enforces the existence of a META-INF directory. Descriptors do not need to be stored in a directory name META-INF.
• [163536] The partition does not start up in JBuilder. Instead, it displays the error message: "Socket connection timed out".
  Workaround : Check that you have the following line in your hosts file.

  127.0.0.1    localhost
  

  The hosts file is located in:
  • Windows: WINDOWS_HOME/system32/drivers/etc
  • UNIX: /etc/
• [162276] WebLogic 8.1 (WebLogic toolkit): If the Servicegen overwrite flag is manually set to false, web services does not get generated if only ejb-based webservices are present.
• [226034] WebLogic 9.0: Currently you are unable to redeploy an EJB class implementation for mapped or exploded EJB modules.

[ top ]

Web Development

Tips

When running a JSP or servlet using JBuilder's internal web browser, the initial time to compile the JSP may cause the server to respond too slowly for the internal browser's time-out value. The server will close the connection and the page will render blank in the Web View. One or two repeated attempts to load the page by hitting Refresh or by placing keyboard focus on the URL field and hitting Enter should load the page. Alternatively, the JSP or servlet can be viewed in an external browser. Typically, an external browser has a generous time-out value that can be configured.

Known problems

• When JBuilder starts a server that is providing the JSP/Servlet service, it attempts to wait for the web container to be loaded before switching to Web View for the desired Launch URI. With some servers, the web container may start responding before all of the web application contexts are loaded. If the desired web application context is not loaded within thirty seconds after the server process has started, you may see HTTP errors in the Web View such as "500 No Context" or "503 Service Unavailable". If this occurs, wait for the server to finish loading, then click the Refresh button in the Web View's toolbar (or load the Launch URL with an external browser).
• [204065] Class files are put in wrong directory in an WAR archive if obfuscation (RetroGuard and ProGuard) is used.
• [171787] If you encounter problems when trying to debug JSPs when using Tomcat 4.1, try this workaround:
  1. Download Tomcat 4.0.x.
  2. Copy jasper-compiler.jar and jasper-runtime.jar from your Tomcat 4.0 installation (TOMCAT_HOME/lib) to the Tomcat 4.1 installation (TOMCAT_HOME/common/lib).
• [161837] Applets that use AWT components may have rendering problems when running in JBuilder's built-in browser.
  Workaround: Comment out addbootpath ../lib/lawt.jar in your bin/jbuilder.config file.
• [159574] Tomcat 4.1: Errors occur when compiling JSPs in subdirectories that are not valid package names (containing invalid characters like '-' or being Java reserved words). See http://issues.apache.org/bugzilla/show_bug.cgi?id=17505 for more information.
• [155264] Tomcat 4.1: Building a WAR file with a ZIP file contained in the dependency results in an error message.
  Workaround: Rename the ZIP file with a jar extension. Or, see if an archive with the JAR extension is available.
• [154615] Trying to debug two JSPs with the same name deployed in different web contexts, always loads the JSP for the web application deployed first. (This is a generic Jasper bug in the latest versions of Tomcat and WebSphere 5.)
• [150650] The cactus.properties file is generated with an incorrect port in the following cases:
  • The wizard is launched with a server running and the user clicks Finish at the first step.
  • The wizard is launched in a project with multiple run configurations with different port numbers for the JSP/Servlet service.

  Workaround:

  1. Select the server run configuration and ensure that the server is not running when the Cactus Setup wizard is launched.
  2. Open cactus.properties in your test directory (test path in the Project Properties dialog, Paths page), then edit the cactus.contextURL property, adding the correct port number. You will have to rebuild the project after doing this.

[ top ]

Team Development

Tips

To take full advantage of CVS capabilities in JBuilder, it is recommended that you use the version of CVS that is installed with JBuilder or later.

For projects that are under version control, it is recommended you do not use "New Folder" feature from the Project Pane. It is better to organize your project using JBuilder's automatic source package discovery, or by choosing Add Files/Packages.

Known problems

• Error: "The CVS Client is either not installed or not located in your PATH. Please install CVS or add CVS to your PATH settings." When using Microsoft Windows 98, you will encounter this error when attempting to use CVS with JBuilder for the first time. To correct this problem, do the following:
  1. Exit JBuilder.
  2. In you JBuilder bin directory, rename the file cvs95.exe to cvs.exe.
  3. Restart JBuilder.
• StarTeam only: Custom tools don't appear in the JBuilder 2006.
  Workaround: The StarTeam integration in JBuilder 2006 is ready to make use of StarTeam Enterprise Advantage custom tools. This feature requires StarTeam Extensions 6.0. You can upgrade the StarFlow Extensions project in their Enterprise Advantage Servers to make use of the tools.
• StarTeam only: The Alternate Property Editors are not embedded in JBuilder 2006--they appear as modal dialogs.
  Workaround: Upgrade your StarTeam Extensions to version 6.0 (even on older servers). Copy the starteam-extensions.jar from the installation directory to your JBuilder lib directory. See the StarTeam Extensions 6.0 readme file for more information.
• [CR 26700] StarTeam only: If process items are required by the project, StarTeam requires you to select a valid process item on the StarTeam page in the Commit Browser for all actions. This should not, however, be required for the following actions: Undo Checkout, Merge, and Handle Individually.
  Workaround: When you perform a Undo Checkout, Merge, or Handle Individually action in the Commit Browser, select a valid process item, but do not select the Mark Selected Process Item As Fixed/Finished/Complete check box.
• [209366] When running Visual SourceSafe 6.0d, JBuilder can hang due to a VSS command not returning if the machine locale setting is not English.
  Workaround: To recover, kill SS.EXE using the Windows Task Manager. If you have to do this, the JBuilder integration with Visual SourceSafe will no longer be functional until the application is restarted.
• [208568] StarTeam continues to check status of files in the repository even when "Modified in Repository" and "Not in Repository" in Project|Project Properties|Decorations are disabled.
• [208405] Opening some Clearcase projects cause the Project Pane to paint very slowly when the project is using the default decorators.
  Workaround: Turn off the "Modified in Workspace" decorators.
• [206525] Placing a project into a Subversion repository with a name that contains extended characters can cause several issues, including:
  • The Annotations page will not display the annotation numbers and user information for each line in a file.
  • You will not be able to pull the same project using the wizards. Project names containing extended characters are corrupted in the browse dialog for the Pull Project From Subversion wizard. If you try to pull a project with a corrupted name, you get a "<project url> does not exist" error and the import operation will fail.
• [205652] Linux and Solaris only: Dragging a requirement from CaliberRM to a source file shows a non-drop icon for the mouse pointer, but it drops the symbol anyway.
• [186445] StarTeam only: JBuilder does not include an encryption library. Without one, users cannot connect to encrypted StarTeam servers.
  Workaround: Please contact StarTeam Developer Support for information on obtaining an appropriate encryption library.
• [178969] StarTeam only: When pulling a project with the folder name having a "/" or "\" character, and then something following it, causes a "String index out of range: -1." error.
• [151112] If a user tries to add more than 4 files to a Visual SourceSafe project at one time, the status/appropriate action of the first 4 files will be displayed in the status and commit browsers, but any remaining files will not be listed.
  Workaround: Add files to the project in increments of 4. Or, add all of the files to the Visual SourceSafe database, then close and reopen the commit and status browsers: all of the source files will be listed.
• [221989] StarTeam only: When a project is already under StarTeam version control, changing the StarTeam server it points to causes the StarTeam node to state that it cannot find the project in the alternate server. Once you change the server description, you cannot open the StarTeam Repository node.
  
  Workaround: Choose Team|Configure StarTeam and switch back to the original server.
• [229634 and 229635] CaliberRM: CaliberRM supports connecting via SSL and supports using non-default ports on the CaliberRM Server. To connect to the CaliberRM server's listening non-default port, in the Configure Connection dialog box, add the port of the SQM Monitor after the host's name. For example, localhost:20003.

[ top ]

Mobile development

Mobile development is a feature of JBuilder Developer, JBuilder Enterprise, and JBuilder Mobile Edition. It provides support for UEI compatible J2ME JDKs, plus the specific vendors listed below.

Installing a J2ME JDK

Mobile development works with any UEI compliant J2ME JDK. It also supports the J2ME CLDC/MIDP JDKs listed below. Of these, only the Sun J2ME Wireless Toolkit 2.1 for Windows is delivered and installed for Mobile development with JBuilder.

[220187] To use other supported JDKs (SDKs), you must download them from the vendor and install them on your computer, then set them up in JBuilder. See Setting up a JDK.

The Solaris and Linux versions of the Sun WTK are available for download from Sun. You can use them with JBuilder Mobile development on the Solaris and Linux platforms, however they are currently unsupported by Sun and have undergone only limited testing.

Note: Palm support has been discontinued in MIDP 2.0. so if you use J2MEWTK 2.0, you won't be able to use MIDP 2.0 features in your Palm development. For more information about Java and Palm development, see Java on the Palm OS at http://www.palmos.com/dev/tech/java/.

Downloading the Nokia Developer's Suite for the Java^TM 2 Platform, Micro Edition

This version of Mobile development does not include the Nokia Developer's Suite for Java ^TM 2 Platform, Micro Edition. You must download it from Nokia and install it to your computer, then configure it in JBuilder. See "Setting up a J2ME JDK" in Developing Mobile Applications for instructions on configuring the JDK.

To download the Nokia Developer's Suite, follow the Nokia instructions below.

Forum Nokia membership is required to download the Nokia Developer's Suite, located in the Java Developer Section of the Forum Nokia Web site. Membership is free of charge.

Download steps

If you are not currently a member of Forum Nokia, you'll need to register.

• For developers in the Americas: http://americas.forum.nokia.com
• For developers in other regions of the world: http://www.forum.nokia.com/reg_form.

Once you have obtained your user name and password, follow the steps below:

1. Log in to Forum Nokia at http://www.forum.nokia.com/.
2. Click on Java^TM Tool link for the Nokia Developer's Suite 2.1 for J2ME^TM.

Note: When you set up the Nokia JDK in JBuilder you need to point to the <jdk_home> directory, which is the parent to the \bin directory where the emulator is installed. For Nokia the <jdk_home> would be <Drive name>\Nokia_Developers_Suite\Emulators\Nokia_6310i_MIDP_SDK_Beta_0_1, or whatever is the current name for the emulator directory.

After installing the Nokia JDK, open JBuilder and configure the JDK. For instructions on configuring a JDK, see "Setting up a J2ME JDK" in the Mobile development setupfile

What's available on Forum Nokia Java Developer Section

• The Nokia Developer's Suite for the Java^TM 2 Platform, Micro Edition download
• Developer's Guide and other documents
• Frequently Asked Questions
• Access to discussion groups

Setting up a Siemens Mobility Toolkit (SMTK)

If you received a version of a Siemens Mobility Toolkit (SMTK) on a CD, follow the Siemens instructions delivered with the CD to install it.

If you want to download any of the available Siemens Mobility Toolkit (SMTK), follow the instructions below.

Download steps

Membership in the Siemens Developers Village is required to download any Siemens Mobility Toolkit (SMTK). Membership is free of charge. The Developers Village is located at http://www.siemens-mobile.com/developer .

If you are not currently a member, go to the Developers Village and click the Registration link. Follow their directions for signing up.

Once you have established a user name and password, log in to the Developers Village and visit the Download Center in the Tools section. Follow the instructions there for downloading and installing a Siemens Mobility Toolkit (SMTK) for any of the supported devices.

After installing the Toolkit, open JBuilder and configure it. See "Setting up a J2ME JDK" in the Mobile development setup instructions.

Setting up the Sprint PCS Wireless Toolkit

If you received a version of the Sprint PCS Wireless Toolkit on a CD, follow the Sprint PCS setup instructions delivered with the CD to install it.

If you want to download the Sprint PCS Wireless Toolkit, follow the instructions below.

Download steps

Membership of the Sprint PCS Application Developer's Program is required to download the Sprint PCS Wireless Toolkit. Membership is free of charge. The Application Developer's Program registration and login page is located at http://developer.sprintpcs.com.

To download the Sprint PCS Wireless Toolkit,

1. If you are not currently a member, go to the Sprint Application Developer's Program registration and login page and click the Register Now! link.
2. Follow the directions for signing up.
3. Once you have established a user name and password, log in to the Application Developer's Program, click the Resources tab, and click Wireless Java in the menu on the left side of the page.
4. Click the link on the Wireless Java page to download the installation program, spcs_jwtk.exe, for the free Sprint PCS Wireless Toolkit.

After installing the Toolkit, open JBuilder and configure it. See For instructions on configuring the SDK, see "Setting up a J2ME JDK" in the Mobile development setup file.

Setting up the Sony Ericsson J2ME SDK

If you received a version of the Sony Ericsson J2ME SDK on a CD, follow the setup instructions delivered with the CD to install it. If you want to download it, follow the instructions below.

Download steps

To download the Sony Ericsson J2ME SDK, you must first sign up as a member of Developer World at the Sony Ericsson Developer World website. The Community Membership level is free of charge.

To download the Sony Ericsson J2ME SDK,

1. Open a web browser and go to Sony Ericsson Developer World at http://www.sonyericsson.com/developer.
• If you have a user name and password, log in to Sony Ericsson Developer World.
• If you are not currently a Developer World member, click the Membership Overview tab and choose Community Membership from the menu at the left. Follow the directions for signing up. You will automatically be logged in.
2. Click on the Docs & Tools tab, then click on the Java tab to go to the Java Docs & Tools page.
3. Scroll down and click on the Sony Ericsson J2ME SDK link to download the .zip file that contains the installation program for the free Sony Ericsson J2ME SDK. The links for downloading the Release Notes and the "Java Developer's Guide" are also on this page if you want to download those.

The latest information about Sony Ericsson phones is located at http://www.sonyericsson.com/

Configuring the SDK in JBuilder

After installing the Sony Ericsson J2ME SDK, open JBuilder and configure it using Tools|Configure JDKs. For more information, see "Setting up a J2ME JDK" in the Mobile Development setup file.

Important: When you choose to install the Java^TM 2 Platform Micro Edition, Wireless Toolkit 2.1 during Mobile development installation, Mobile development adds two custom menu items to the Tools menu that point to Wireless Toolkit configuration and utility tools: Emulator Preferences, and Emulator Utilities. If you want to use a J2MEWTK installed in a location other than in the JBuilder folder, you must modify the entries for these Tools menu items so they point to the J2MEWTK installation you want to use.

To modify the settings for each of these custom Tools menu items,

1. Choose Tools|Configure Tools on the Mobile development main menu.
2. Select Emulator Preferences in the Custom Command Line Tools list and click the Edit button.
3. Click the ellipsis button for the Program field, and browse to the <j2mewtk_home>\bin\prefs.bat file where the J2MEWTK you want to use is installed. Click OK to return to the Configure Tools dialog box.
4. Repeat steps 2 and 3, this time selecting the Emulator Utilities item, and browsing to <j2mewtk_home>\bin\utils.bat.

Of course, you always have the option of deleting the contents of the <JBuilder_home>\j2mewtk2.1 folder and installing a new version in that same directory. As long as the directory structure remains the same, you would not need to edit the Tools menu items.

Setting up a J2ME JDK

Setting up a JDK in Mobile development consists of creating a library file for the JDK. Download and install the J2ME JDK you want to use, then follow the steps below to set it up. Do this for each J2ME JDK you have downloaded and installed.

Note: JDK and SDK are synonymous terms in JBuilder documentation.

1. Launch Mobile development.
2. Choose Tools|Configure JDKs.
3. Click New to open the New JDK wizard.
4. Click the ellipsis button and select the <jdk_home> directory where the JDK is installed.

   Note: <jdk_home> is the parent to the \bin directory where the JDK is installed. For example, if your J2ME JDK is in the JBuilder folder, the <jdk_home> will be <JBuilder_home>\jdk_home\.

5. Type in a name for the new JDK library file, then click OK.
6. Click OK to close the Configure JDKs dialog box.

To make this JDK the default for all projects, choose Project|Default Project Properties, and select it in the JDK field on the Paths page. Alternatively, you can choose this JDK when you create a project with the Project wizard, or set it for an existing project by changing the Project Properties.

Setting up Mobile development for J2ME Palm Application development

Note: Palm support has been discontinued in MIDP 2.0. so if you use J2MEWTK 2.0, you won't be able to use MIDP 2.0 features in your Palm development. For more information about Java and Palm development, see Java on the Palm OS at http://www.palmos.com/dev/tech/java/.

Before you begin any Palm development, go to the Palm OS® Emulator site at http://www.palmos.com/dev/tech/tools/emulator/, and read about the requirements for Palm development and the use of ROM images. This web page is updated regularly and contains important information for Palm developers. It is also the URL from which you download the Palm Emulator, sign up for the Palm OS Developer Program, and obtain ROM image files, among other things.

You are strongly urged to sign up for the Palm OS Developer Program so you can obtain debug ROMs for development. In the meantime, if you don't have access to a ROM yet, and you'd like to start development right away, you can upload a ROM image from most Palm devices into the Palm OS Emulator using a serial cable. However, the ROMs on devices are non-debug ROMs, therefore they cover up errors and are not suitable for real development.

Also, if you did not choose to install the J2ME Wireless Toolkit when you installed Mobile development, you need to download it and install it locally before beginning Palm OS development for J2ME.

Once you've installed Mobile development, the J2ME Wireless Toolkit, and Mobile development, follow the steps to set up your Mobile development working environment for developing J2ME Palm applications:

1. Download the Palm OS Emulator from http://www.palmos.com/dev/tech/tools/emulator/, and extract it to a directory called <drive name>\Palm\emulator.

   Important: The Palm OS Emulator executable file (emulator.exe) must be in a directory that matches its name. If you want to install the Palm OS Emulator to a directory other than <drive name>\Palm\emulator, you must rename emulator.exe to match the directory name in which it resides. For example, if you put the emulator in a directory called <local drive>\Palm\pose, rename emulator.exe to pose.exe.

2. Download one or more ROM image files from Palm to the directory containing the Palm emulator. See the Palm OS Emulator site at http://www.palmos.com/dev/tech/tools/emulator/ for directions and links for doing this.

   Alternatively, you can upload a ROM image directly from a Palm handheld device following these steps:

   1. Locate the file ROM Transfer.prc in the Palm OS directory. Use the Install tool in the Palm Desktop organizer software to install it.
   2. Place the handheld in the HotSync cradle connected to the serial port on your computer, and synchronize with the handheld to install ROM Transfer.prc on the handheld.
      
   3. Exit the HotSync Manager.
   4. Transfer a ROM file to the emulator.
      If this is the first time you've run the ROM Transfer program, Palm OS Emulator displays a Startup dialog box. Click Download to begin the ROM transfer.
      If it is not the first time you've run the emulator, Palm OS Emulator usually restarts the session you most recently ran. In this case, right-click on the emulator display and select Transfer ROM.

   For more information on downloading or transferring ROM images, see the document UserGuide.pdf delivered with the Palm OS Emulator.

3. Open Mobile development and choose Tools|Configure JDKs to setup a new JDK for the J2ME Wireless Toolkit. See "Setting up a J2ME JDK" earlier in this document.

4. Create a new project: Choose File|New Project to open the Project wizard and create a new project for your Palm application. On Step 2 of the Project wizard, click the ellipsis button by the JDK field and select the J2ME JDK. Make any other desired changes in the wizard, then click OK to close the wizard.

5. Set the project properties to use the PalmOS_Device: Choose Project|Project Properties, and click the MIDlet tab on the Run page. Select PalmOS_Device from the Emulator Device drop-down list, then click OK to close the dialog box. For more information on creating projects, see "Creating and managing MIDP projects" in the Mobile development Developer's Guide.

6. Create the MIDlet: Choose File|New and click the Micro tab. Double-click the MIDlet icon to run the MIDlet wizard and create the MIDlet and Displayable files. For more information on creating MIDlets, see "Creating a MIDP user interface" in the Mobile development Developer's Guide.

7. Code your application, then compile and debug it. Fix any errors, then rebuild and save. See "Building MIDP applications"in the Mobile development Developer's Guide for more information on compiling and running.

8. Click the Run button on the Mobile development toolbar to run the application in the Palm OS® Emulator.

   The first time you run a J2ME application using the Palm emulator, you will be prompted for the location of the emulator.

   This information is kept at <J2mewtk>\wtklib\devices\PalmOS_Device under the J2ME Wireless Toolkit installation directory. It uses the Converter.jar file to convert a JAD and JAR files to a PRC file.

9. Specify the ROM, Palm Device, Skin, and Ram Size to use for the session: Once the emulator is running, right-click on it and choose New to open the New Session dialog box where you can select these options.

For additional information on using the Palm OS Emulator, see <Palm>\Docs\UserGuide.pdf delivered with the emulator. Also check the Palm OS Emulator site at http://www.palmos.com/dev/tech/tools/emulator/ for updated emulators, ROMs, skins, and instructions.

Known problems

• [227771] If you use WTK 2.2 and earlier, and you get the message "ALERT: java/lang/ClassFormatError: Bad version information" when you launch the MIDlet, you may need to set the target VM in JBuilder to any targets other than Java 2 SDK, v 5.0 (generics enabled). This option is on the Build|Java page of the Project Properties dialog box.

[ top ]

XML

Tips

If transformation of your XML document fails, check to see if you are using the correct version of the stylesheet specification, http://www.w3.org/1999/XSL/Transform, and not the working draft.

Castor now requires 2001 schema support, <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">. If an older version is used, an error or exception might occur. The Castor sample has been updated: <JB_HOME>/samples/tutorials/XML/databinding/fromSchema/Castor.jpx. The same is true for XML schema validation. You can find the latest Xerces schema samples with 2001 schema support in <JB_HOME>/extras/xerces/data/.

Known problems

• [209131] Cocoon fails to run with Borland Enterprise Server 6.
  Workaround: In the partition.xml file (example location: \BES\var\domains\base\configurations\jbuilder\mos\jbpartition\adm\properties\partition.xml), add "org.apache.xerces,org.w3c.dom,javax.xml,org.xml.sax,org.xml.dom" to the container prefixes so the container element looks like this: <container system.classload.prefixes="java.,javax.ejb.,!javax.servlet.jsp.jstl.,javax.servlet.,javax.jms.,org.apache.log4j.,org.apache.xerces,org.w3c.dom,javax.xml,org.xml.sax,org.xml.dom" verify.on.load="true" classloader.policy="per_module" classloader.classpath="lib/app;${install.root}/lib/tomcat/jasper/jasper-compiler.jar;${install.root}/lib/tomcat/jasper/jasper-runtime.jar" use.validating.parser="true"/>
• [208653] Cocoon fails to run with WebSphere 5.0. This happens because WebSphere 5.0 shipped with IBM's JDK 1.3 and Cocoon is on JDK 1.4.
  Workaround: If possible, upgrade to WebSphere 5.1.0.4.
• [178821] Cocoon doesn't run with Tomcat 4.1.
  Workaround: This is a Tomcat/JDK 1.4.2 incompatibility issue. One way to work around this is to copy all the latest XML-related jars (xalan.jar, xerces.jar, and xml-apis.jar) into the <tomcat home>/common/endorsed subdirectory.
• [172500] Checking the "Selections" Trace option while transforming an XML file causes transformation to fail.
  Workaround: Download and install the latest version of Xalan from http://xml.apache.org/xalan-j/.
• [109759] There is an inconsistency in the requirement for putting quotation marks around table names in the XMLDBMSTable and XTable components. XTable requires quotation marks; XMLDBMSTable does not.
• [109254] Trying to transfer data to Interbase using XMLDBMSBeans causes JBuilder to hang.
  Workaround: Download the InterClient/InterServer 2.02 patch from http://www.borland.com/devsupport/interbase/interclient.
• [108694] After entering a value in KeyEditor for the XMLDBMSTable customizer, the user has to press Enter in order for the value to be accepted. Also, the actual value shows "<NL>" at the end, which should be removed.

[ top ]

Debugger

Remote debugging

When attaching to a process running on a remote computer, the default address has changed from 5000 to 3999.

To view this change,

1. Choose Project|Project Properties.
2. Click the Run tab.
3. Choose a runtime configuration click Edit.
4. Click the Debug tab. On the Debug page, choose Enable Remote Debugging, then choose Attach. Note that the Address option defaults to 3999.

   The port number/address that you set in this field should match the address parameter that you use when you run your program from the command line on the remote computer.

If you are running Windows XP, do not use 5000 as the port number/address through which the debugger communicates with a remote computer. Windows XP reserves this port for the Universal Plug & Play.

Tips

• When a class is compiled without debug information, the debugger will not be able to see any local variable information. However, it can see the "this" object. If you are debugging and only the "this" object shows up, it could mean that the class was built with no debug information. It could also mean that there are no local variables in the class.
• In JDK 1.3.0, 1.3.0_01, and 1.3.0_02, debugging using the classic VM is much faster than debugging with HotSpot. If you see a noticeable slowdown in your program when you debug it, try adding the -classic option as the first VM parameter in the runtime configurations for your project before you debug. Note that JBuilder will do this by default as appropriate for these JDKs.
• JBuilder now has a checkbox in the Configure JDKs dialog (use Tools|Configure|JDKs) that allows you to set whether the classic parameter will be automatically added to the debug command line when using this JDK in your project. JBuilder tries to default this checkbox appropriately. If the JDK is one that does not support a classic VM, this option will not be selected.
• If you are experiencing intermittent crashes when debugging in JBuilder under Windows, this could be caused by the presence of the dt_shmem.dll in the JDK. This DLL is used as an implementation of the debugging protocol on Windows (used in communication between the debugger and debuggee), and causes intermittent problems. To avoid using this DLL, remove it from any JDKs you are planning to use for debugging, and make sure that any directories that contain this DLL do not appear on your system PATH. If you do this, the alternate dt_socket.dll will be used for the debugging protocol. This DLL does not appear to have the problems of dt_shmem.dll.

Known problems

• [148698] Debugging a sample project fails when <JB_HOME> contains international characters (entered during installation). Debugging a new project whose files are stored in a directory with international characters also fails.
  Workarounds: Try one of the following:
  • Change the J2SE installation path that the debugger uses from <JDK_HOME>\jdk1.4 to <JDK_HOME>jdk1.4\jre.
  • Copy <JDK_HOME>\jdk1.4\jre\bin\dtshmem* and <JDK_HOME>\jdk1.4\jre\bin\148 dt_socket* to <JDK_HOME>\jdk1.4\bin, then run the debugger with the J2SE installation path in your debugger set to the value: <JDK_HOME>\jdk1.4.
• [135160] Linux only: While using the remote debugging feature of attaching JBuilder as a client to a running remote process, a sun.io.MalformedInputException in sun.io.CharToByteSingleByte.convert() is thrown.
  Workarounds:
  • Disable breakpoints for 'All uncaught exceptions' in the Breakpoints dialog (Run|View Breakpoints).
  • Edit JB_HOME/jdk1.4/jre/lib/font.properties and insert a "#" at the beginning of every line that contains the string "symbol".
• [134354] Stopping on an exception breakpoint in a JSP displays strange behavior. When the program stops, the point of execution is not shown. The debugger status label shows a line in the java code of the translated JSP and the JBuilder status bar says "Can not locate Jsp1$jsp.java from project source/class path". The execution point for the exception breakpoint will not be shown in Tomcat unless a line-breakpoint is also defined in that JSP file.
• [100401] Linux only: Choosing Step Over causes JBuilder to freeze.
  Workaround: Add the -classic option as the first VM parameter in the runtime configurations for your project when debugging.

[ top ]

Designer

The Designer supports code generated by VisualAge (versions 3 and 4). You can view the source files generated by VisualAge, and use the Designer with these source files without having to modify them in any way. Use the Designer to add additional components, copy and paste, move components between containers, move to first, move to last, and change their properties and constraints.

Tips

Red beans due to this extending an abstract class

When JBuilder needs to instantiate an object to be the this object, it can't instantiate the object you're designing. To circumvent this problem, JBuilder instantiates the superclass of the this object. If the superclass is abstract, it can't be instantiated. It's necessary to provide a concrete proxy class.

You can add your own proxy objects in the user.properties file. The syntax is

designer;proxy.<fully qualified name of abstract class>=<fully qualified name of concrete class to be used as proxy>

For example,

designer;proxy.java.awt.Component=com.borland.jbuilder.designer.dt.ComponentProxy

The proxy class must

• Extend the abstract class in question.
• Be concrete (not be declared abstract itself).
• Be public.
• Have a default public constructor.

Warning: Generally, it's very strongly recommended that you avoid altering the user.properties file. If you must alter it, save the original version first, as a backup.

For more information on red beans and their causes, see "Handling red beans" in the "Advanced topics" chapter of Designing Applications with JBuilder.

Known problems

• [209302] Adding an EJB component to the designer displays java.lang.ClassNotFoundException: javax.ejb.EJBObject createDefaultPropertyEditor(javax.ejb.EJBObject) in the Message pane. The Message pane now cannot be closed, not even by Ctrl-Alt-M.
• [206769] An IllegalAccessException is thrown when dropping any components from the EJB tab to the designer.
• [205424] Cannot load the UI Designer with a server set for the project.
  Workaround: Do not set a server for the project.
• [186526] If you have more than one file open in the Designer, and then change the Look and Feel for a file to a Look and Feel different from the one under which JBuilder is running, the content of the Design and Source views become out of synch with the other files.
  Workaround: Close JBuilder and restart. If you want to test out your application in different Look and Feel, the recommended way is to do it by changing the JBuilder Look and Feel by choosing Tools|Preferences|Browser|Look & Feel rather than selecting the Look & Feel from context menu in the Designer.
• [108178] Attempting to define an event handler with the same name as the event results in generated code that overflows the stack when executed. This code is completely legal, it just calls itself recursively.

[ top ]

OpenTools

If certain calls to the Open Tools API Browser class are made from within the jbInit() method of a class being designed by the UI Designer, JBuilder will exhibit strange repainting and response issues. The calls that definitely exhibit this behavior include:

• Browser.findBrowser()
• Browser.getActiveBrowser()
• Browser.getBrowsers()
• Browser.getBrowsersNonZ()

The solution is to move these calls outside of the class's jbInit() method into another method, such as the constructor.

[ top ]

Borland Enterprise Server

The development license for Borland Enterprise Server is included in your JBuilder product license. The 6.x license will work with the following versions of BES: 6.0RP1 and 6.5.

JBuilder 2006 Developer includes:

• One free Borland Enterprise Server 6.5, AppServer Edition (J2EE) development license.

JBuilder 2006 Enterprise includes:

• One free Borland Enterprise Server 6.5, AppServer Edition (J2EE) development license
• One free Borland Enterprise Server 6.5, VisiBroker Edition (CORBA) development license.

Additional licenses are required for deployment.

The Linux version of Borland Enterprise Server included with JBuilder 2006 supports Red Hat Linux. It does not support SuSE Linux.

Known Problems

• The BES tutorials might not work.
• [210026] Index.html has three links to BES, for "What's New", install instructions, and release notes. All three links point to readme.html, a short file that doesn't provide "what's new" info, install instructions, or release notes.
  Workaround: See the documentation included with BES for that information.
• If you are using BES 6.0RP1 or BES 6.5, you will need to go to install the latest server patch for JBuilder before you can use the BES server in JBuilder 2006. To download the BES AppServer 6.5 patch, go to http://www.borland.com/downloads/registered/download_jbuilder.html or go directly to BES AppServer 6.5 Patches. To download the BES App Server 6.0.1 patch go to BES AppServer 6.0.1 Patches.
• Borland Enterprise Server version 6.x is not available on Macrovision FLEXlm.
• [228506] You will be prompted to insert the BES6.5 Disk when using SuSE. However, the Redhat version of BES is the only version that is supported in this release of JBuilder.

[ top ]

JDataStore

As of JBuilder 2006, JDataStore is a deprecated feature and should not be used except for legacy support or temporary development. You should use a different DBMS for deployment purposes.

[ top ]

Sun Java System Application Server

Known Problems

• [218270] If a WSDL mapping file contains more than one identical WSDL part name for different messages, the application fails to deploy on the server.
  
  Workaround: Change the wsdl:part name attribute values so that no two are identical.
  
  
• [215197] Failure to start the server after multiple start ups and shut downs. Workaround: Change the default jms port in domains.xml and restart the server.
  
  
• [213180] Default deploying of Cactus Web Modules fails. You need to make the following changes:
  1. Edit the file server.policy in the SERVER_HOME\domains\<domainName>\config directory.
  2. Modify the following property and add write permission:
     
     

     permission java.util.PropertyPermission "*", "read,write";

• [213108] Default deploying of Axis based Web Services fails. You need to make the following changes:
  1. Edit the file server.policy in the SERVER_HOME\domains\<domainName>\config directory.
  2. Add the following properties:
     
     

     permission java.lang.RuntimePermission "createClassLoader";
     
     permission java.lang.RuntimePermission "getClassLoader";

• [217308] When using the Sun 8 server with Axis Web Services, in order to test and view deployed services, you need to do following:
  1. Edit the server.policy file and add the following to the grant tag:

     permission javax.management.MBeanPermission "*", "*";

  2. Add <jbuilder>/lib/wsdl4j.jar to the Required Libraries in the Enterprise|Configure Servers dialog box.
• [218270] If a WSDL mapping file contains more than one identical WSDL part name for different messages, the application fails to deploy on the server.
  
  Workaround: Change the wsdl:part name attribute values so that no two are identical.
  
  
• [215197] Failure to start the server after multiple start ups and shut downs. Workaround: Change the default jms port in domains.xml and restart the server.
  
  

[ top ]

JBoss 4.x

Known problems

• [211854] For JBoss 4.0, the following changes are required to make JBoss 4.0 work with J2EE 1.3 web services:
  
  
  1. Open the Web Services Designer and click the Axis Flow tab.
  2. Expand the Services node and for each of the services, bring up the inspector and change the Provider QName. Clear out the Namespace field and enter Handler for Class field. Make sure to uncheck the Regenerate Element On Source Change check box.
  3. Expand the service node in the structure pane, right click on the Parameters node and choose Add. Enter handlerClass for Name and org.jboss.net.axis.server.EJBProvider for Value for the newly created parameter.
  4. Create a new library that includes these two jars:
     
     
     • <jbossInstalldir>/client/axis-ws4ee.jar
     • <jbossInstalldir>/docs/examples/jboss.net/jboss-net-client.jar>
  5. Add this new library to the project.
  6. Move the Axis library to the top of the Required Libraries list before compiling the project.
  
  
  

  This is not needed for JBoss 4.0.2 or 4.0.3RC1.

• [226696, 226496] Some versions of some web containers don't follow the Servlet 2.3 specification rule of calling ServletContextListener listeners defined in TLD files in the META-INF directory of a jar.
  See http://java.sun.com/j2ee/javaserverfaces/docs/ReleaseNotes.html#issues
  Running a JavaServer Faces technology Web application in such a container requires you to manually declare the ServletContextListener instance. The listener-class you need to specify is com.sun.faces.config.ConfigureListener.
  Workaround: To run a JSF app on a JBoss server you need to specify the following in web.xml.

  <listener>
      <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
    </listener>
  

  
  
• [222458] When you create a new EJB 2.1 module using JBoss 4 as the server, you'll see an error about <port-uri>.
  jboss.xml generated by JBoss 4.0 and 4.0.2 are both validated against jboss_4_0.dtd which enforces <port-component-uri>
• [225582] WSDL links are not working correctly for EJB service and Java service when you deploy a Java service and an EJB service at the same time in JBoss4.0. However they work when using JBoss 4.0.2 and 4.0.3.

WebLogic

Known problems

• [208055] Failure to invoke a jsp page in a mapped web module with ClassCast Exception.
  Workaround: To invoke the jsp page, deactivate and then activate the module.
• [221077] WebLogic 9.0: No tag insight is available for Weblogic-cmp-rdbms-jar.xml for EJB 2.1 modules.
• [224042] WebLogic 9.0: Unable to redeploy any archive (EJB, War, Ear).

[ top ]

Unix

Tips

Printing on Linux and Solaris platforms

A workaround for users on Unix platforms who do not need to use AWT components in the designer and want to be able to select a printer that is different than lpr is to comment out the line in the jbuilder.config file that adds the LightWeight Toolkit to the boot path as shown:

# Put the Lightweight Toolkit on the boot path
#addbootpath ../lib/lawt.jar

Applets

In order to run an applet on Solaris or Linux from within JBuilder, you must add the Open Tools SDK library to your project. Failing to add this library can lead to an exception about a "NoClassDefFoundError:AppletTestbed." This problem currently affects some of the applet samples, including the Primes Swing sample.

Known problems

• [206399] The LD_LIBRARY_PATH set in the environment does not get passed to JBuilder. This causes problems for the DB2 JDBC driver, as it requires the library path be set to locate native components of the driver.
• [151119] Solaris only: The automounter on Solaris might mount the CD-ROM to a drive name with a '#' in it. This causes the installation to fail. If this occurs, reboot your machine before installing JBuilder.
• [100311] Warnings are issued when installing JBuilder:

  Warning:
    Name: HorScrollBar
    Class: XmScrollBar
    The specified scrollbar value is greater than the maximum scrollbar value minus the scrollbar slider size.
  

  
  Workaround: Ignore: the warning is harmless.
• [90559] When a new window pops open (CodeInsight, code templates, etc.), focus to the editor is lost. (This works properly using KDE.)
  Workaround: (For GNOME users) Go to the Control Center and change the "Focus Behavior" so that "Dialog windows inherit the focus from their parent" is turned off.

[ top ]

Samples

The samples.html file should be viewed in JBuilder or from the link in the Welcome Project if you want to use the links to load the project files in JBuilder. However, if you configure your file associations so that JBuilder projects are associated with JBuilder, you can view samples.html in most web browsers, and the links to projects will work.

Known problems

• "Error # 914: unable to write to output directory". If you have installed JBuilder as root but are running as a regular user, you need to copy the entire samples tree to a directory in which you have full read/write permissions in order to run them. While it is possible to copy projects individually from the sample tree, there are several samples which require access to files in peer-level directories. Such samples have been modified to look automatically for such files relative to the default sample tree hierarchy and display a message at runtime indicating the path being used to locate such files.

  An easy way to copy the entire samples tree is to use the cp -R command. For example, to copy the tree to a samples subdirectory of your home directory, do the following:

  % cd
  % cp -R /usr/local/jbuilder/samples
  

• [73147] You must compile the JDataStore, dbSwing and DataExpress samples before using them in the Designer. This will make classes and data available to the designer.
  If you open a sample in the Designer and get an error message such as Filename property set to null or URL cannot be null, open the file in the editor, modify the source (such as a adding and removing a space), then rebuild the project. You should now be able to open the project in the Designer without errors.

[ top ]

Performance

These are some suggestions for improving local performance of JBuilder.

• You can get smoother garbage collection performance by enabling incremental garbage collection. Use the following VM setting to do this:

  vmparam -Xincgc
  

  It is worth noting that the incremental garbage collector, while smoothing GC hiccups, also slows the VM down noticeably. We suggest using this only if you experience long garbage collection-induced pauses while using JBuilder.

• You can reduce the amount of background source parsing for the structure pane by increasing the parsing time delay. To do this, right click the structure pane and select properties. Increase the Parse Delay setting.

[ top ]

International

Installing to a Japanese NEC machine:

[75607] If you are installing JBuilder to a Japanese NEC computer and the install program causes an operating system error message saying that "Drive C: is not ready... the drive door may be open...", press the <Ignore> button in this dialog. Install will then complete normally. (The <Abort> button should also work.)

Japanese Fonts on Linux:

[75704][75705] If you experience problems displaying Japanese fonts on Linux, you may need to update the file, <jdk1.3.1>/jre/lib/font.properties.ja. JavaSoft's web site has instructions on how to do this in Japanese: Directions to modify the font.properties file (in Japanese).

Command Line Compiler:

• [79877] (Windows platforms only) European versions of the command line compilers (bcj and bmj) may display accented characters incorrectly in a console window. The workaround is to invoke the compiler as follows (Note: <path_to_JBuilder>/lib/jbuilder.jar must be on your classpath):

  java -Dfile.encoding=Cp850 com.borland.compiler.frontend.Main -encoding Cp1252 myFile.java
  

  The first encoding option above is passed to the Virtual Machine and the second encoding option is passed to the compiler. Please note that this example assumes Code Page 850 is used in the console window (as shown by the chcp command), and that your java files are encoded in Code Page 1252 (which is the case when a Windows based editor was used, rather than an "old style" DOS-based editor).

  If your program sends accented characters to the console window, they will be displayed correctly if you use the following (assuming your console window uses Code Page 850, as shown by the DOS chcp command):

  java -Dfile.encoding=Cp850 myClassFile
  

Other Known Problems:

• [70027] When IntlSwingSupport is dropped on a Frame in the designer, it may be instantiated after other class members such as a JFileChooser, JOptionPane, or JColorChooser, which means the translated resources are loaded too late for initial display purposes. Instantiating IntlSwingSupport as early as possible during your application startup will fix this problem.
• [72107] Undo <Ctrl_> under Emacs keymap is mapped to <Ctrl Shift -(hyphen)> using Japanese Keyboard.
• [72519] Undo <Ctrl_> under Emacs keymap does not work using French Keyboard. The workaround is to use <Ctrl x><u> or use the keymap editor to customize the keymapping.
• [73279] If the environment variable, LC_CTYPE, is set to the POSIX 'C' locale, the Sparc Compose key may not function for certain versions of Xlib client libraries.
• [74063] (Japanese OS only) Under bold and italic attributes, the cursor will stop in the middle of a character. To workaround the problem, add the following line to JBuilder2006/bin/jbuilder.config:
vmparam -Dprimetime.editor.useVariableWidthFont=true
  After the update, remove ~/.jbuilder2006/user.properties before launching JBuilder.
• [107292] A patch is available for JSPs running in Japanese patch. See http://www.ingrid.org/jajakarta.
• [109510] French keyboard under Solaris and Linux only: Shortcut keys for setting numbered bookmarks (Ctrl + Shift + "#") and jumping to numbered bookmarks (Ctrl + "#") don't work. Use the keymap editor to customize the keymapping.
• [124670] When using the ClearCase integration: if a filename contains extended characters, the file content is cleared out after an un-checkout operation.
• [125556] The KeyPressed event is not called when accented characters are used from the French keyboard.
• [130987] RedHat 7.2 with KDE: Cannot key in the reverse single quote (single grave accent) '`' and the circumflex accent '^' in a Java application using a German keyboard layout.
• [133891] Entering the Euro symbol, "€", as part of the directory path for JBuilder in the installer will cause JBuilder to throw an exception. The Euro character displays correctly in the JBuilder text box of the installer. However, when JBuilder is installed, the directory name will have a question mark in place of the Euro character.
  Workaround: Do not use spaces or currency symbols in the path names when installing JBuilder.
• [148006] Linux only: Stopping XIM causes JBuilder to hang.
• [154222] The license file might be displayed incorrectly in some locales. A space character is displayed in places where a grave accent or smart quote should appear.
• [156594] JBuilder opens a JSP file as an ISO-8859-1 encoded file when the file does not contain the value "charset=Shift_JIS" in its header.
  Workaround: The JSP 1.2 specification is followed strictly in JBuilder. In JBuilder 2006, we provide a way to override the default JSP encoding. You can add the system property "jsp.default.encoding.override" to specify the encoding they want in their specific applications. For example, add the following line to the jbuilder.config file:

  vmparam -Djsp.default.encoding.override=Shift_JIS
  

• [230322] (Japanese only) When creating a web module on the Redhat platform, UTF-8 is used instead of the default native encoding.

[ top ]

Documentation

If your version of JBuilder does not contain the documentation PDF files on one of the product CDs, you can download them from the JBuilder Product Documentation web site: http://info.borland.com/techpubs/jbuilder. Also, check the JBuilder Product Documentation web site for updates to the documentation.

For the latest JBuilder FAQ's and TI's, please visit:

• FAQ's: http://bdn.borland.com/all/0,1435,c|3|10,00.html
• TI's: http://bdn.borland.com/all/0,1435,c|3|9,00.html

Links from the JBuilder documentation to the JDK 5 documentation are broken.

[227148] Links to JDK 1.4 documentation still work but may not provide the correct information now that JDK 1.5 is being used.

Developing Web Applications

Version information for third party software and links to third party web sites may not be up to date. See the JBuilder 2006 New Features Guide for updated information.

Developing Mobile Applications

[226238] Although the Developing Mobile Applications PDF contains information on i-mode, JBuilder no longer provides i-mode support. Some information about i-mode has been removed, and some links to that information no longer work.

Struts

[222384] When running the Struts blank project for Struts 1.2.4 you will receive the following messages:
"index.jsp": org.apache.jasper.JasperException: File "/tags/struts-logic" not found
"Welcome.jsp": org.apache.jasper.JasperException: File "/tags/struts-bean" not found

Workaround: After building the project, you need to update the uri values in both index.jsp and Welcome.jsp to match with the uri defined in Struts library.

Change from
<%@ taglib uri="/tags/struts-logic" prefix="logic" %>
<%@ taglib uri="/tags/struts-bean" prefix="bean" %>
<%@ taglib uri="/tags/struts-html" prefix="html" %>
<%@ taglib uri="/tags/struts-logic" prefix="logic" %>

to index.jsp
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
in Welcome.jsp
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>

Tutorial Updates

XML tutorial 3: Data binding from a DTD using BorlandXML
In the "Adding an employee record" step, before adding a new Employee, run the program.

XML tutorial 7: Transferring data with the template-based XML database components
In the "Transferring data with the XTable component" step, the XTableOut filename in "Output File:" control already has the HTML extension.

Struts tutorial:
In step 9, code that you enter into TilesAction.java needs to be changed.
return actionMapping.findForward("tilesDefinition");
should be
return mapping.findForward("tilesDefinition");

Simple Servlet tutorial:
In "Step 4: Adding code to the servlet" item 2 says insert where it should say "replace code doGet(request, response); with the code below..."

Creating a JSP using the JSP Wizard tutorial:
By default on Step 4 "Generate error page" is selected by default.
Note that Yellow is selected by default for the page background.

[ top ]

Getting Help

For the latest JBuilder FAQs and Technical Information Notes (TIs), please visit:

• FAQs: http://bdn.borland.com/all/0,1435,c|3|10,00.html
• TIs: http://bdn.borland.com/all/0,1435,c|3|9,00.html

Installation Instructions

For installation instructions, see install.html.

[ top ]