Borland JBuilder 2006

Release Notes

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

Getting Help
Installation

[ top ]

System Requirements

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

Borland® JBuilder® 2006 Enterprise

Windows®

Linux®

SolarisTM

JBuilder®2006 Developer

Windows®

Linux®

SolarisTM

[ 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 GoogleTM 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 GoogleTM 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:

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

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

[ 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:

Windows Issues:

Solaris and Linux Issues:

[ top ]

Web Services

Known Problems

[ top ]

Enterprise JavaBeans (EJB)

Known problems

[ 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

[ 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

[ 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 JavaTM 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.

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 JavaTM Tool link for the Nokia Developer's Suite 2.1 for J2METM.

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

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.
  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 JavaTM 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

[ 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

[ 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

Known problems

[ 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

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

[ 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:

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:

JBuilder 2006 Enterprise includes:

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

[ 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

[ top ]

JBoss 4.x

Known problems

WebLogic

Known problems

[ 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

[ 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

[ top ]

Performance

These are some suggestions for improving local performance of JBuilder.

[ 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:

Other Known Problems:

[ 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:

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:

Installation Instructions

For installation instructions, see install.html.

[ top ]