NetBeans Visual Web Pack 5.5 Release Notes

NetBeans Visual Web Pack 5.5 provides an environment for rapidly building web applications with Ajax-enabled JavaServer Faces components, support for drag-and-drop binding to data sources, and more.


Note: The Ajax components included with NetBeans Visual Web Pack 5.5 are samples only, and are not meant for production applications.

Note: Update 1 for NetBeans Visual Web Pack is now available. See the Change Notes for more information

System Requirements

This topic specifies the prerequisites that must be met before you start to install NetBeans Visual Web Pack 5.5.

System Setup

The following table lists the minimum hardware and operating system requirements to run NetBeans Visual Web Pack 5.5:




Disk Space

Operating System

Supported Browsers

Solaris SPARC

UltraSPARC III at 750-MHz processing speed

1 GB

130 MB

Solaris 10 OS

Sun-supported Mozilla 1.7

Solaris (x86 Platform Edition)

Intel Pentium 4 (or equivalent) at 1 GHz processing speed

1 GB

130 MB

Solaris 10 OS

Sun-supported Mozilla 1.7

Microsoft Windows

Intel Pentium 4 (or equivalent) at 1 GHz processing speed

1 GB

130 MB

Windows 2000 Professional Edition (Service Pack 4),
Windows XP Professional Edition (Service Pack 2)

Internet Explorer 5.5 Service Pack 2 (Windows 2000)
Internet Explorer 6 Service Pack 2 (Windows XP)


Intel Pentium 4 (or equivalent) at 1 GHz processing speed

1 GB

130 MB

Red Hat Fedora Core 3 (except when running in the zh_CN locale and possibly other Asian locales - see the Known Issue Rendering Problems below.)

Firefox 1.0.4 (minimum)

Mac OS

1 GHz PowerPC G4
1.83 GHz Intel Dual Core

1 GB

130 MB

Macintosh OS 10.4, 10.4.5

Safari 1.2.1 minimum (Safari 2 minimum for OS 10.4.5), Mozilla 1.6

Required Software

The following software must be installed before you install NetBeans Visual Web Pack 5.5:

  • NetBeans IDE 5.5.
  • Java SE Development Kit (JDK) 5.0 Update 6 (version 1.5.0_06) or higher.

    If you do not have an installation of JDK 5.0 Update 6 or higher, you cannot proceed with the installation. You can download this JDK from the Java SE Downloads page.

    Note that Mac OS X installations require Java 2 Standard Edition (J2SE) 5.0 Release 4. You can download this JDK from the Apple Downloads page. Search for "J2SE" to locate this release.
  • An application server

    To take advantage of Visual Web Pack's sample applications and databases, and to develop visual web applications using Java EE5, use Sun Java System Application Server 9, Platform Edition, the open source Java EE 5 application server. For more information, see Java EE Downloads.

Supported Technologies

NetBeans Visual Web Pack 5.5 supports the following technologies:

  • Enterprise JavaBeans (EJB) 3.0
  • JAX-WS 2.0
  • Java Persistence (JSR-220)
  • JavaServer Faces 1.2 (JSR-127)
  • Java Servlet 2.5
  • JavaServer Pages (JSP) 2.1
  • Struts 1.2.9
  • Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.6
  • Java APIs for XML Registries (JAXR) 1.0
  • Java API for XML Processing (JAXP) 1.2
  • JavaServer Pages Standard Tag Library 1.1

Note: using versions of JBoss, WebLogic, or Struts other than those explicitly listed could result in unpredictable IDE behavior because they are External interfaces and not controlled by the project team.

NetBeans IDE 5.5 has been tested with the following application servers:

  • Sun Java System Application Server PE 9.0 Update Release 1
  • Sun Java System Application Server PE 8.2
  • Tomcat 5.5.17
  • JBoss 4.0.4
  • WebLogic 9.1

If you are using the GlassFish application server, note that it is recommended to run the final build of GlassFish V1 UR1 in order to work with NetBeans IDE 5.5 .

Supported Databases, JDBC Drivers, and Deployment Containers

NetBeans Visual Web Pack 5.5 is tested on the following databases and drivers:

Oracle driver tested on the Oracle database:

Driver LocationOracle Database 10g Release 2 JDBC Drivers
Driver Versions Oracle Database 10g Release 2 (
Driver JAR File ojdbc14.jar
Driver Classnames oracle.jdbc.driver.OracleDriver
URL Formats jdbc:oracle:thin:@//hostname:port/database
Example URL jdbc:oracle:thin:@//localhost:1521/ora9i

Microsoft driver tested on the SQL Server database:

Driver Location Microsoft SQL Server 2005 JDBC Driver 1.1
Driver Version Microsoft SQL Server 2005 JDBC Driver 1.1
Driver JAR File sqljdbc.jar
Driver Classname
URL Format jdbc:sqlserver://hostname:1433;databaseName=database;selectMethod=cursor
Example URL jdbc:sqlserver://localhost:1433;databaseName=travel;selectMethod=cursor

IBM drivers tested with the DB2 database:

Driver LocationDB2 Personal Developer's Edition: Redistributable JDBC Type 4 Driver (requires registration)
Driver VersionRedistributable DB2 JDBC Type 4 driver v8 fixpack 11
Driver JAR Files Type 4
  • db2jcc.jar
  • 2jcc_license_cu.jar
Driver Classname
URL Format (Type 4) jdbc:db2://hostname:port/database
Example URL jdbc:db2://localhost:50002/sample

Note: The IBM drivers support both Type 2 (native) and Type 4 (pure Java). To force the drivers to run in Type 4, add a property: driverType = 4 when connecting to the database.

MySQL drivers tested with the MySQL database:

Driver Location Download Connector/J 5.0.3 (tar.gz)
Download Connector/J 5.0.3 (zip)
Driver Version MySQL® Connector/J 5.0.3
Driver JAR Files mysql-connector-java-5.0.3-bin.jar
Driver Classname
URL Format jdbc:mysql://hostname:port/database
Example URL jdbc:mysql://localhost:3306/sample

DataDirect drivers tested with Oracle, SQL Server, DB2 and Sybase databases:

Driver LocationDataDirect Connect for JDBC, Release 3.6 Service Pack 1
Driver Versions DataDirect Connect for JDBC - 3.6
DataDirect Connect for JDBC - 3.6.07
Driver .jar FilesDataDirect Driver .jar Files
  • base.jar
  • util.jar
  • spy.jar
  • resource.jar
  • oracle.jar
  • sybase.jar
  • sqlserver.jar
  • db2.jar
  • informix.jar
Driver Classnames DataDirect Driver Classes
  • com.ddtek.jdbc.sqlserver.SQLServerDriver
  • com.ddtek.jdbc.db2.DB2Driver
  • com.ddtek.jdbc.sybase.SybaseDriver
URL Formats DataDirect URL Formats
  • jdbc:datadirect:oracle://server_name[:portNumber];SID=database
  • jdbc:datadirect:sqlserver://server_name[:portNumber];databaseName=database
  • jdbc:datadirect:db2://server_name[:portNumber]databaseName=database
  • jdbc:datadirect:sybase://server_name[:portNumber
Example URLs jdbc:datadirect:oracle://localhost;SID=ora9i

Firewall Applications

Enabled firewall applications can prevent some components from being configured correctly during the installation process. Consult your firewall documentation to determine if your firewall should be disabled before installation.


Configuration Information

Information on configuring NetBeans Visual Web Pack 5.5 for databases and applications servers can be found in the Installation Guide.

If Visual Web Pack is configured to use Sun Java System Application Server 9, Platform Edition then a bundled database server (Java DB) is included. For more information on Java DB, see Java DB at a Glance. Once the Sun Java System Application Server is configured, and after the IDE is restarted, a sample database named Travel and a database connection for Travel are configured. If the home directory, located under <HOME>/.netbeans/5.5, is removed, the databases will remain intact until the next time Sun Java System Application Server is reconfigured. The sample database directory is located in the home directory .netbeans-derby.

Note: Before resolving a databse connection to the Travel database, you must start the Java DB.

Bundled Database

If you install Sun Java System Application Server, you can set up the bundled Java DB database to work with NetBeans Visual Web Pack 5.5 as well.

To set up the Java DB server for a standalone NetBeans IDE 5.5 installation:

  1. Launch the IDE.
  2. Register Sun Java System Application Server in the NetBeans IDE Runtime window as described in the Installation Guide.
  3. Select Tools > Options, and in the Options dialog, click Advanced Options.
  4. Expand IDE Configuration > Server and External Tool Settings and select Java DB Database to verify the database settings.

Restoring Database Connections

When opening Java Studio Creator projects that have components bound to rowsets in Visual Web Pack, the IDE fails to find the data sources. When importing projects into Visual Web Pack, the IDE advises you to backup the project as you will not be able to re-open it in Java Studio Creator. To resolve missing data connections, you first add the database driver and then reconnect the project to the database. You do not need to add the database driver if the project uses for Java DB, and you installed Sun Java System Application Server as described under Bundled Database.

To add the database driver:
  1. Open the Runtime window.
  2. Expand the Databases node. Right-click Drivers and and select New Driver.
  3. In the New JDBC Driver window, click Add. Navigate to the database's .jar file and click Open.
  4. Select the Driver Class, type a name for the database (or keep the default), and click OK.
  5. Right-click the Databases node and select New Connection.
  6. In the New Database Connection dialog:

    1. Select the database from the Name drop-down list.
    2. Type the Database URL.
    3. Type the user name and password.
    4. Click OK.
  7. Under the Databases node, Right-click the database URL associated with the database and Right-click the database connection and choose connect. You may be prompted for a password.

See Supported Databases, JDBC Drivers and Deployment Containers for more information on drivers and database URLs.

To resolve the database connection:
  1. Open the Projects window. The IDE searches for missing data connections. Note that the larger the project, the longer this process takes.

    When the IDE determines that data connections are missing, it badges the project node icon and displays the project name in red.
  2. Right-click the project with the missing data connection, and choose Resolve Database Problems from the pop-up menu.
  3. In the Resolve Data Source(s) dialog, select the database name and click Add Data Connection.
  4. In the Add Database Connection dialog, select your database from the Server Type drop down list, provide the requested information, and click OK.

    For Java Studio Creator applications that use Java DB, type the User ID and Password associated with the application. For example, the User ID and Password for the CorporateTravelCenter project are both travel. The database URL has the following format: jdbc:derby://host_name:port_number/database_name. For example, the database URL for the Travel database bundled with Java DB, on the default port is jdbc:derby://localhost:1527/travel.


Sample Applications

To use any of Visual Web Pack's sample applications, you must create a new Visual Web project that uses the application, and then connect the project to the sample database if one is provided.

Updates to the Visual Web Pack might include new sample databases and sample applications. After an update, to see if there are new sample applications, choose File > New Project to open the New Project wizard, and then choose Samples > Visual Web to see the list of sample applications in the right pane. To create a sample application:

  1. Choose File > New Project.

    The New Project Wizard opens.
  2. In the Categories pane of the New Project Wizard, expand the Samples node and select Visual Web.
  3. Select the sample project from the Projects pane and click Next to continue.
  4. Type the name of the project in the Project Name field.

    The IDE suggests a name that you can edit.
  5. Based on the project name, the IDE suggests the Project Location and Project Folder. You can change the project location.

    The IDE creates a folder name based on the information you enter. The IDE suggests a default Java package for the project. You can change the Java package name by typing in a new name.
  6. Ensure that Java Blueprints is selected in the Source Structure drop-down list.
  7. Ensure that the Sun Java System Application Server is selected in the Server drop-down list.

    If you do not see the Sun Java System Application Server in the list, you must register the server with NetBeans as described in the Help topic Registering a Sun Java System Application Server Instance.
  8. Select Java EE5 from the Java EE Version drop-down list, and then click Finish to create the project.


Change Notes

This section describes changes to NetBeans Visual Web Pack from release to release.

NetBeans Visual Web Pack 5.5 ML (Multi-language)

The ML release adds language support for Japanese, Simplified Chinese, and Brazilian Portuguese. The following issues have also been addressed in this release:

Internet Explorer 7 AddRemove Listbox Headers

Description: Headers for adding and removing listboxes did not extend to edge of their associated listboxes. This has been fixed by removing the float:left style in the AddRmvHwzDiv class selector.

Internet Explorer 7 Anchors

Description: Formerly, in pages created with hyperlinks pointing to an anchor, IE 7 did not automatically jump to the anchor.

AbstractDesignInfo.acceptFiliation restricts drops on ActionSource

Description: This fix allows non Woodstock-based ActionSource components to become parent components.

NetBeans Visual Web Pack 5.5 FCS

Upgrading to Production Release

Instructions for upgrading from NetBeans Visual Web Pack 5.5 Technology Preview are in the Installation Guide.

Downloaded component libraries no longer display automatically in the Palette.

Description: The NetBeans Visual Web Pack 5.5 UI has changed. To display a component library in the Palette, you just first import its complib file into the IDE, then add it to a project. Imported complibs do not display in all projects, only in projects to which they have been added.

For more information, see the tutorial Downloading and Importing Ajax and Other Components and the Help topic About Component Libraries.

Update 1 Available for NetBeans Visual Web Pack.

Description: This update fixes the InSync Source Modeler bug (Visual Web Pack breaks Drag and Drop functionality in SOA projects).

To install this update:

  1. Choose Tools > Update Center from the main menu. This will launch the Update Center wizard.
  2. In the Update Center Wizard, select NetBeans Visual Web Pack Update Center and click Next.
  3. In the panel labeled Select Modules to Install, select InSync Source Modeler Module, click Add to include in the install, and click Next.
  4. Accept the license agreement. Once the modules are downloaded, click Finish. You will be prompted to restart the IDE to complete the installation.

Note: Update 1 is for NetBeans Visual Web Pack 5.5 release. This update is visible to NetBeans Visual Web Pack 5.5 Technology Preview users also, but the update will fail on Technology Preview with a message that module dependencies are not satisfied. Technology Preview users upgrade to the Production Release as described in the Installation Guide.

This update also fixes the NetBeans Enterprise Pack 5.5 users' issue of not being able to Drag and Drop in SOA projects.


Known Issues

This section covers unresolved issues for this release. For further information, see the NetBeans Visual Web Pack FAQ.

Sample Database

Sun Application Server 9 Platform Edition requires IDE restart.

Description: To use the Travel Database with Sun Application Server 9 PE, you must restart the IDE after choosing the application server in the Servers window.

Clean and Build

Clean and Build fails after application deployment.

Description: Application deployment returns the error "Unable to delete file ...\build\web\WEB-INF\lib\appbase.jar".

Workaround: Stop and restart the application server and deploy the application again.


JSF 1.2 converter runtime error messages are different than those in JSF 1.1.

Description: The conversion error messages for JSF 1.2 are much more detailed than those in JSF 1.1. For more information, see the converter topics in the online help.

Vista Installation

Installation of NetBeans Visual Web Pack on the Vista operating system will fail if the installer is not pointed to JDK 1.5_11 or later.

Description: Although JAVA_HOME and PATH point to jdk1.5_11 or 6, the installer may still try to install based on an earlier installed JDK on the system.

Workaround: Make sure that the installer is actually running on the later JDK by using the switch -is:javahome <path to 1.5.0_11 home>.

Button Appearance

Button text on the Editing Toolbar is missing or truncated.

Description: On Microsoft Windows XP, using the Windows XP display style, button text is replaced with ellipses. This problem is related to JDK 5.0 Update 8 (version 1.5.0_08).

Workaround: Change your display style to Windows Classic as follows:

  1. Choose Start > Settings > Control Panel.
  2. On the Control Panel, double-click Display.
  3. On the Appearance Tab, choose Windows Classic style under Windows and Buttons.

Buttons Display Incorrectly in IE7

When displayed in IE7, all button components may be rendered with an incorrect width.

Description: This problem occurs when the button is placed using absolute positioning. For example, when NetBeans Visual Web Pack uses absolute positioning to place components in Grid Layout Mode, this problem may occur.

IE7 expects a value to be specified for the width of buttons. If a width attribute is not specified, the width is set to width:auto, which results in the button's width being set to the entire available width of the button's container element. For example, if the button style has left=130px then the button will start at 130px left and will expand to the width of the <body> element.

Workaround: There are several different ways to solve this issue in NetBeans Visual Web Pack:

  • Specify the width property for the button, or resize the button in the IDE to make the IDE assign a width to the button.
  • In the IDE, drop the button into a Group Panel component to put the button inside a span tag. In this case there is no need to set the positioning as the IDE sets the positioning for the Group Panel component. For example, the JSP code of a Button inside a Group Panel component may look like this:
    <webuijsf:panelGroup binding="#{Page1.groupPanel1}" id="groupPanel1" style="position: absolute; left: 240px; top: 168px">
    <webuijsf:button binding="#{Page1.button1}" id="button1" text="Button"/> </webuijsf:panelGroup>

Component Libraries and JBoss

Components of the webui component library (based on JSF 1.1/J2EE 1.4), bundled with NetBeans Visual Web Pack 5.5, work poorly.

Description: When a project is created, the classpath on the container is checked and when a MyFaces implementation is found, that implementation takes precedence. Removing the MyFaces implementation forces the application to bundle the JSF-RI libraries.

Workaround: Move the following directory outside of the default directory before creating Visual Web Pack projects for that container:


Java EE5 Deployment

Application deployment hangs.

Description: Java EE 5 deployment of applications to Sun Java System Application Server hangs due to the server's deployment manager depending on code that is not thread safe.

This issue seems limited to multiprocessor or multicore computers running Windows XP.

Workaround: Restart the IDE, then using the Server Manager:

  1. Restart the application server if necessary.
  2. Undeploy all applications.
  3. Redeploy the applications.
If it is not possible to start or stop the application server, stop all Java processes via the task manager before restarting the IDE.

Renaming Project Folders

Renaming a project folder throws IllegalStateException.

Description: IDE throws IllegalStateException when reopening a project with a renamed folder or reopening a folder with a renamed page.

Workaround: Only rename folders from within the Source Packages node. Right-click the folder under this node and select Refactor > Rename from the pop-up menu. Note that the IDE does not currently support renaming the default Bean package.

Binding to Data

Binding a Drop Down List component to table data returns exception.

Description: Using MySQL, attempting to bind the Drop Down List component to table data returns an IllegalArgumentException.

Workaround: When the error occurs, close the Bind to Data dialog and open it again. If this fails, close and reopen the project.

ViewData SQL Command

Inserting a new line or space results in incorrect empty return.

Description: A query made in the View Data window that concludes with whitespace or a carriage return is not executed.

Web Services

Web service package not visible under JDK 1.5_06 in projects using J2EE 1.4.

Description: In projects in which web services has been added, the import statement should autocomplete in the Java view (that is, the web service package should be visible to the application), but the IDE returns "No suggestions".

Workaround: Build the project first, then the Java source editor will provide suggestions.

Distorted Images

Background images are scrambled or missing in the browser upon postback.

Description: When a postback occurs, background images set via a background-image style with a relative URL, such as background-image: url(./resources/flower.gif), are scrambled or missing in the browser.

Workaround: The following fix works for both Java EE 4 and EE5 projects. Manually set the background image using code such as the following:

<h:panelGrid binding="#{Page1.gridPanel1}" id="gridPanel1"
    style="background-image: url(/WebApplication1/resources/flower.gif); 
                height: 200px; left: 312px; top: 240px; position: absolute" width="312"/>
In some browsers, the Grid Panel in the above excerpt may need to have at least one child in order for the background image to appear. For instance, the child could be a Static Text component with the escape property set to False and the text property set to a non-breaking space (&nbsp;):
<h:panelGrid binding="#{Page1.gridPanel1}" id="gridPanel1"
style="background-image: url(/WebApplication1/resources/flower.gif); height: 200px; left: 312px; top: 240px; position: absolute" width="312">
<webuijsf:staticText binding="#{Page1.staticText1}" escape="false" id="staticText1" text="&amp;nbsp;"/> </h:panelGrid>

Note that while this workaround is effective at runtime, it will cause the image to disappear at designtime.

Checkbox Component

The readOnly property of the Checkbox and Checkbox Group components does not work,

Description: These components remain clickable even after setting its attribute to readOnly.

Workaround: Use the disabled attribute so that the component renders when it applies but must not be changed.

Also, use scripting to prevent changes on an element that is readOnly. Here, button1_action toggles the readOnly property of checkbox1:

<?xml version="1.0" encoding="UTF-8"?>
<jsp:root version="1.2" xmlns:f="" xmlns:h="" xmlns:jsp="" xmlns:webuijsf="">
< contentType="text/html;charset=UTF-8" pageEncoding="UTF-8"/>
<webuijsf:page binding="#{Page1.page1}" id="page1">
<webuijsf:html binding="#{Page1.html1}" id="html1">
<webuijsf:head binding="#{Page1.head1}" id="head1">
<webuijsf:link binding="#{Page1.link1}" id="link1" url="/resources/stylesheet.css"/>
<webuijsf:script binding="#{Page1.script1}" id="script1"><![CDATA[
function preventIfReadOnly(element) {
if (element.readOnly != false) {
//element is readOnly, so prevent change by returning false
return false;
//allow change by returning true
return true;
<webuijsf:body binding="#{Page1.body1}" id="body1" style="-rave-layout: grid">
<webuijsf:form binding="#{Page1.form1}" id="form1">
<webuijsf:checkbox binding="#{Page1.checkbox1}" id="checkbox1" label="Checkbox" onClick="return preventIfReadOnly(this);" style="position: absolute; left: 192px; top: 192px"/>
<webuijsf:button actionExpression="#{Page1.button1_action}" binding="#{Page1.button1}" id="button1"
style="position: absolute; left: 216px; top: 288px" text="Toggle checkbox readOnly property"/>
<webuijsf:messageGroup binding="#{Page1.messageGroup1}" id="messageGroup1" style="position: absolute; left: 432px; top: 120px"/>


URL property limited to ISO-8859-1 characters.

Description: Uploaded file components not displayed for the jp locale. File names appear correctly in the browser and in the log file, but the image does not display when the file name is in mbyte character sets. When the orignal filename of an uploaded file contains UCS characters, the src attribute of the img tag is not rendered correctly. Thus when the browser fetches the image, it gets a File Not Found error and nothing appears in the browser window.

Workaround: Have the application limit the URL property to ISO-8859-1 characters. For example, provide a separate translation step from the ISO 10646 UCS character set to ISO-8859-1. It is best to avoid using UCS characters entirely.

Bundled Database

Cannot connect to database for projects created before deletion of user directory and reinstallation of IDE.

Description: The JDBC driver is lost when the user directory is deleted, therefore the user cannot resolve missing data connections.

Workaround: Before deleting the user directory copy the jdbc-drivers folder to an external directory and return it to the user directory after reinstallation.

Renaming Variables

When the user renames a property by selecting Bean Patterns > Property > Rename, the NetBeans IDE does not treat the rename as full refactoring. New names of variables renamed in this way are not propagated across a project.

Description: The IDE renames getter and setter methods if the user answers Yes in the pop up dialog that covers these methods, however, other references to these methods are not updated. When an application is deployed in which only the name of a variable, for example that of a bean property, is changed, the IDE throws a compiler error.

JDBC Drivers

Applications utilizing data sources fail if JDBC driver is not copied to server.

Description: NetBeans does not copy the JDBC driver JAR files to the deployment container.

Workaround: Copy the JAR files manually into the container's class path.

Woodstock Components

Projects created in Visual Web Pack Technology Preview do not build in the production release.

Description: The IDE fails to copy all the contents of the WebUI components library at build time, resulting in build failure

Workaround: Remove the old WebUI components library and add the new WebUI components library as follows:

  1. In the Projects window, right-click on the project and select Properties.
  2. Select Libraries, select the Web UI Components library package, and click Remove. Click OK to close the dialog.
  3. Right-click on the project again and select Properties.
  4. Select Libraries and click Add Library. In the Add Libraries dialog, select Web UI Components and click Add Library. In the Project Properties window, click OK.
  5. Right-click the Project and select Clean and Build Project.

Imported Projects

It is not possible to deploy the imported Java Studio Creator CorporateTravelCenter project on Sun Java System Application Server.

Description: EJB clients fail to connect on imported projects.

Workaround: Edit the web/WEB-INF/sun-web.xml file by changing the jndi name from jdbc/Travel_RaveGenerated_1129222276 to jdbc/Travel.

Button Width in Internet Explorer

IE 7 only: Default button width not honored.

Description: When the button width is not explicitly set, IE 7 resizes the button to the width of the container.

Workaround: Explicitly set button widths in the Visual Designer.

Session Data Lost in Internet Explorer

IE 6 and IE 7 only: Session lost after navigating 20 pages.

Description: In projects with more than 20 pages, session data is lost and information saved in a session bean attribute is reset to Null once user navigates past about page 20. This is not an issue in Firefox or other browsers.

If browser security is set to Medium, the session is renewed at about page 22; if set to High, the session continues to page 30. The session is maintained when cookies are disabled.

Workaround: In Internet Explorer:

  1. Select Tools > Internet Options.
  2. Select the Privacy tab.
  3. Change settings from Medium (the default) to High or Block All Cookies.
  4. Press OK.
  5. Restart all instances of Internet Explorer.

Rendering Problems

IDE text unreadable on Red Hat Fedora Core 3 using the zh_CN locale.

Description: When running the IDE on Red Hat Fedora Core 3 in the zh_CN locale and possibly some other Asian locales, the text may be unreadable because of rendering problems. This problem is a result of font support issues with the JDK on the Fedora Core distribution, so this problem also might apply to other Java applications running on Fedora Core.

Workaround: There is no safe workaround for the rendering problem on Red Hat Fedora Core 3, so it is best to use a different Linux distribution or operating system in these locales. We have verified that this problem does not occur on Red Hat Enterprise Linux 3.

Java Server Pages

With Visual Web modules enabled Java Server Pages hidden in free form projects.

Description: If you downloaded and installed NetBeans Visual Web Pack 5.5 Technology Preview between October 29,2006 and November 3, 2006, you might have found that enabling Visual Web modules hides Java Server Pages in free form projects. This is documented in NetBeans issue 88510. This problem has been fixed in downloads available after November 4, 2006.

Workaround 1: Download the patch from the Visual Web Pack Update Center as follows:

  1. From the IDE's main menu, choose Tools > Update Center.

    The Update Center wizard opens. If you are working behind a firewall, you must configure the proxy server. Click Proxy Configuration and enter your proxy information in the dialog box.
  2. Ensure that NetBeans Visual Web Pack Update Center is selected.
  3. Click Next in the Update Center wizard. The wizard checks for available updates and new modules, then opens the Select Modules to Install pane if there are updates or new modules available.
  4. In the left panel, select Complib (version 1.1) and JSF Project Core (version, then click the Add button to move them to the Include in Install panel.
  5. Click Next, then read and accept the license agreement.

    The Update Center wizard downloads the patch.
  6. Click Next to install the module into the IDE, click Finish, and click OK to restart the IDE.

Workaround 2: Disable the NetBeans Visual Web Pack 5.5 modules as follows:

  1. From the IDE's main menu, choose Tools > Module Manager.
  2. In the Module Manager, uncheck the box in the Active column associated with Visual Web.
  3. Once the IDE has updated the modules, click Close.

These modules can be re-enabled at any time using the same steps.



Documentation for NetBeans Visual Web Pack 5.5 is provided in the form of web-based guides and the IDE's help system. You can use the following documents to get started:


More Information

You can also find useful information on the NetBeans Project web site. Since the NetBeans IDE is an open-source project, the web site also provides access to source code, an issue database, information on creating your own NetBeans modules, and much more.

For more information, visit

The NetBeans Visual Web Pack FAQ is located at


Not logged in. Log in, Register