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.
System Requirements
CaliberRM Updates
Peer to Peer Collaboration Updates
Known Issues
Getting Help
- 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
Installation
The system requirements for each of the Borland JBuilder editions are listed below:
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.
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.
These issues are organized by product area.
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.
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:
/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.
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.
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.
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.
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.
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.
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.
-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).oldjava
command does not recognize high ASCII characters in a class name.findfast.exe
. This program can be
manually disabled from your control panel.Note: Blackdown JDKs are not supported for this version of Optimizeit Enterprise Suite.
Note: IBM JDK 1.2.2 is not supported for this version of Optimizeit Enterprise Suite.
-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.
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
.build.xml
properties Ant page.JB/lib/jb-axis-ant.jar
, and added it to "Libraries containing custom ant tasks" in Project properties|Build|Ant.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
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
build_WebLogic.xml
.servicegen
element by adding the following attribute:
overwrite="false"
log4j-1.2.8.jar
Axis may not work. log4j-1.2.8.jar
to the required libraries in the project properties. Each server provides it's own log4j-1.2.8.lib
. -Dvbroker.agent.port=<smart agent port> -Dborland.enterprise.licenseDir=<USER_HOME> -Dborland.enterprise.licenseDefaultDir=<BES_install>/licensewhere
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.hosts
file.
127.0.0.1 localhostThe
hosts
file is located in:
WINDOWS_HOME/system32/drivers/etc
/etc/
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.
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
).addbootpath ../lib/lawt.jar
in your bin/jbuilder.config
file.jar
extension. Or, see if an archive with the JAR extension is available.cactus.properties
file is generated with an incorrect port in the following cases:
Workaround:
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.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.
bin
directory, rename the file cvs95.exe
to cvs.exe
.starteam-extensions.jar
from the installation directory to your JBuilder lib
directory. See the StarTeam Extensions 6.0 readme
file for more information.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.localhost:20003
.
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.
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/
.
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.
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:
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
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.
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.
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.
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,
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.
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.
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,
The latest information about Sony Ericsson phones is located at http://www.sonyericsson.com/
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,
<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.<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 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.
<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\
.
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.
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:
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
.
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:
ROM Transfer.prc
in the Palm OS directory. Use the Install tool in the Palm Desktop organizer software to install it.ROM Transfer.prc
on the handheld.For more information on downloading or transferring ROM images, see the document UserGuide.pdf
delivered with the Palm OS Emulator.
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.
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.
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.
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.
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.
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.
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.
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/
.
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"/>
xalan.jar
, xerces.jar
, and xml-apis.jar
) into the <tomcat home>/common/endorsed
subdirectory.When attaching to a process running on a remote computer, the default address has changed from 5000 to 3999.
To view this change,
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.
-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.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.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
.<JB_HOME>
contains international characters (entered during installation). Debugging a new project whose files are stored in a directory with international characters also fails.
<JDK_HOME>\jdk1.4
to <JDK_HOME>jdk1.4\jre
.<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
.sun.io.MalformedInputException
in sun.io.CharToByteSingleByte.convert()
is thrown.
JB_HOME/jdk1.4/jre/lib/font.properties
and insert a "#" at the beginning of every line that contains the string "symbol".-classic
option as the first VM parameter in the runtime configurations for your project when debugging.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.
this
extending an abstract classWhen 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
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.
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.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.
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.
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.
wsdl:part name
attribute values so that no two are identical.domains.xml
and restart the server.permission java.util.PropertyPermission "*", "read,write";
permission java.lang.RuntimePermission "createClassLoader"; permission java.lang.RuntimePermission "getClassLoader";
server.policy
file and add the following to the grant
tag:
permission javax.management.MBeanPermission "*", "*";
<jbuilder>/lib/wsdl4j.jar
to the Required Libraries in the Enterprise|Configure Servers dialog box.wsdl:part name
attribute values so that no two are identical.domains.xml
and restart the server.Handler
for Class field. Make sure to uncheck the Regenerate Element On Source Change check box.handlerClass
for Name and org.jboss.net.axis.server.EJBProvider
for Value for the newly created parameter.<jbossInstalldir>/client/axis-ws4ee.jar
<jbossInstalldir>/docs/examples/jboss.net/jboss-net-client.jar>
This is not needed for JBoss 4.0.2 or 4.0.3RC1.
TLD
files in the META-INF
directory of a jar. http://java.sun.com/j2ee/javaserverfaces/docs/ReleaseNotes.html#issues
com.sun.faces.config.ConfigureListener
.web.xml
.
<listener> <listener-class>com.sun.faces.config.ConfigureListener</listener-class> </listener>
jboss.xml
generated by JBoss 4.0 and 4.0.2 are both validated against jboss_4_0.dtd
which enforces <port-component-uri>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
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.
Warning: Name: HorScrollBar Class: XmScrollBar The specified scrollbar value is greater than the maximum scrollbar value minus the scrollbar slider size.
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.
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
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.These are some suggestions for improving local performance of JBuilder.
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.
[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.)
[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).
<path_to_JBuilder>/lib/jbuilder.jar
must be on your classpath):
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 thejava -Dfile.encoding=Cp850 com.borland.compiler.frontend.Main -encoding Cp1252 myFile.java
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
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.JBuilder2006/bin/jbuilder.config:
vmparam -Dprimetime.editor.useVariableWidthFont=true
~/.jbuilder2006/user.properties
before launching JBuilder."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
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.
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.
[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.
[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" %>
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.
For the latest JBuilder FAQs and Technical Information Notes (TIs), please visit:
For installation instructions, see install.html
.