NetBeans IDE 6.5 Release Notes

NetBeans IDE is a modular, standards-based integrated development environment (IDE), written in the Java programming language. The NetBeans project consists of an open source IDE written in the Java programming language and an application platform, which can be used as a generic framework to build any kind of application.

Contents

What's New in 6.5

NetBeans IDE 6.5 is a significant update to NetBeans IDE 6.1 and includes the following changes:

  • PHP support with code completion, Xdebug and web service features.
  • JavaFX 1.1 supports animation, graphics and media codecs for rich content application development for desktop and mobile devices.
  • New Support for Groovy and Grails.
  • Improved JavaScript, AJAX and Ruby support.
  • Automatic Compile and Deploy on Save for Java and Java EE applications.
  • Improved database support: SQL history, SQL completion, and results viewing and editing improvements.
  • Improved Java ME support for Data Binding, SVG and Custom Component creation.
  • GUI Builder: Support for Nimbus and simple class names.
  • JUnit: single test method support.
  • Debugger: Redesign of Step into feature.

For information about the main development features in NetBeans IDE, see the NetBeans IDE 6.5 Information page.

Supported Technologies


NetBeans IDE 6.5 supports the following technologies and has been tested with the following application servers. If you plan to use versions other than those explicitly listed, please note that you may encounter unpredictable IDE behavior as a result of the technologies being external interfaces which the project team has little or no control over.


Supported technologies:
  • Java EE 5 and J2EE 1.4
  • JavaFX 1.1
  • Struts 1.2.9
  • Spring 2.5
  • Hibernate 3.2.5
  • Java API for RESTful Web Services (JAX-RS) 1.0
  • Java API for XML-based RPC (JAX-RPC) 1.6
  • PHP 5.2
  • Ruby 1.8
  • JRuby 1.1.4
  • Rails 2.1
  • Groovy 1.5
  • Grails 1.0
  • VCS
    • CVS: 1.11.x, 1.12.x
    • Subversion: 1.3.x, 1.4.x, 1.5.x
    • Mercurial: 1.0.x
    • ClearCase V7.0


Tested application servers:
  • Sun Java System Application Server 9.0 (GlassFish V1)
  • Sun Java System Application Server 9.1 (GlassFish V2)
  • Sun GlassFish Enterprise Server v3 Prelude
  • Sun Java System Application Server PE 8.2
  • Tomcat 5.5
  • Tomcat 6.0.18
  • JBoss 4.0.4
  • WebSphere 6.0
  • Websphere 6.1
  • WebLogic 9.2
  • WebLogic 10


Note: If you are using the GlassFish application server, it is recommended that you run GlassFish V2 in order to work with NetBeans IDE 6.5.

System Requirements

NetBeans IDE runs on operating systems that support the Java VM (Virtual Machine) and has been tested on the platforms listed below.

Note: The IDE's minimum screen resolution is 1024x768 pixels.


Supported Operating Systems

Minimum Hardware Configurations

  • Microsoft Windows XP Professional SP3:
    • Processor: 800MHz Intel Pentium III or equivalent
    • Memory: 512 MB
    • Disk space: 750 MB of free disk space


  • Microsoft Windows Vista:
    • Processor: 800MHz Intel Pentium III or equivalent
    • Memory: 512 MB
    • Disk space: 750 MB of free disk space


  • Ubuntu 8.x:
    • Processor: 800MHz Intel Pentium III or equivalent
    • Memory: 512 MB
    • Disk space: 650 MB of free disk space


  • Solaris OS version 10 (SPARC):
    • Processor: UltraSPARC II 450 MHz
    • Memory: 512 MB
    • Disk space: 650 MB of free disk space


  • Solaris OS version 10 (x86/x64 Platform Edition):
    • Processor: AMD Opteron 1200 Series 1.8 GHz
    • Memory: 512 MB
    • Disk space: 650 MB of free disk space


  • Macintosh OS X 10.5 Intel:
    • Processor: Dual-Core Intel
    • Memory: 512 MB
    • Disk space: 650 MB of free disk space

  • Macintosh OS X 10.5 PPC:
    • Processor: PowerPC G4
    • Memory: 512 MB
    • Disk space: 650 MB of free disk space

    For more information, see Using NetBeans on Mac OS X.

Recommended Hardware Configurations

  • Microsoft Windows XP Professional SP3:
    • Processor: 2.6 GHz Intel Pentium IV or equivalent
    • Memory: 1 GB
    • Disk space: 1 GB of free disk space

  • Microsoft Windows Vista:
    • Processor: 2.6 GHz Intel Pentium IV or equivalent
    • Memory: 1 GB
    • Disk space: 1 GB of free disk space

  • Ubuntu 8.x:
    • Processor: 2.6 GHz Intel Pentium IV or equivalent
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Solaris OS version 10 (SPARC):
    • Processor: UltraSPARC IIIi 1 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Solaris OS version 10 (x86/x64 platform edition):
    • Processor: AMD Opteron 1200 Series 2.8 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Macintosh OS X 10.5 Intel:
    • Processor: Dual-Core Intel
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Macintosh OS X 10.5 PPC:
    • Processor: PowerPC G5
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space
    For more information, see Using NetBeans on Mac OS X.



NetBeans IDE is also known to run on the following platforms:

  • OpenSolaris 2008.11
  • Java Desktop System 2
  • Microsoft Windows 2000 Professional SP4
  • Mac OS X 10.4.11 Intel/Power PC
  • Various other Linux distributions, such as Red Hat Enterprise Linux

Note: While the above system requirements apply to most configurations of the IDE, some areas of NetBeans Web and Java EE support are particularly demanding on system resources, especially when used in combination with various application servers. For best results when developing Web and Java EE applications, make sure that your system meets at least the recommended system requirements.

Required Software


NetBeans IDE runs on the J2SE (Java SE Development Kit) JDK 5.0 Update 14 and higher (including JDK 6.0), which consists of the Java Runtime Environment plus developer tools for compiling, debugging, and running applications written in the Java language.

You can download the JDK for your platform from one of the sites listed below:

Note: You can download archived versions of the JDK at http://java.sun.com/products/archive/index.html.

top


Compatibility


When you first run the IDE, you can import a subset of the settings you used in previous versions of NetBeans IDE. If you choose not to import settings from a previous release, the IDE opens using the default settings.

Note: The IDE only recognizes previous installations where the user directory resides in the default location. It does not recognize installations where you have specified a user directory using the --userdir switch. If you would like to import settings from an IDE that the installer does not recognize, download an archive version of the IDE instead of using the installer.

Note: If you edit the Project Properties in NetBeans IDE 6.5 for a project that was created in NetBeans IDE 4.1 or earlier, the project will no longer work in the earlier NetBeans IDE versions.


top


JavaFX 1.1 SDK Availability

The JavaFX 1.1 SDK enables rich content application development and is available bundled with the IDE or by adding plugins to an existing installation.

  • JavaFX 1.1 SDK bundled with the IDE. (download)
  • Adding the plugin to an existing IDE installation:
    1. In the IDE Main Menu go to: Tools > Plugins
    2. In the Plugins dialog select the Available Plugins tab and find the JavaFX SDK and JavaFX 1.1 plugins. Note: you may need to click the Reload Catalog button to see the JavaFX plugins.
    3. Check the box in the Install column next to the JavaFX SDK and Java FX 1.1. Click Install.

Note: The minimum supported version of the JDK for JavaFX 1.1 is JDK 6 Update 7 for Windows and JDK 5 Update 13 for Mac OS.

Note: For additional information about system requirements, supported features and known issues, please refer to the JavaFX 1.1 SDK Release Notes.

top


UML Module Availability

The UML diagram editors are completely rewritten for this release. The complexity of the new features caused development delays that resulted in the following changes:

  • UML is not in the NetBeans 6.5 installer. UML was moved from the full installer to the Update Center and can be installed via the Tools > Plugins menu in the IDE. The UML module is also available in zip file format.
  • UML Support in 6.5. Five diagram types are supported: activity, class, sequence, state and use case diagrams. These diagrams are automatically upgraded from your pre-6.5 UML projects when saved in the new version of the UML module.

top


SQL Editor and Databases

There have been changes made to the database functionality in NetBeans 6.5. They are as follows:

  • Upgraded Drivers. The MySQL drivers included in NetBeans IDE have been updated to version is 5.1.6.
  • Tested Drivers

    NetBeans IDE 6.5 has been tested with the following databases and drivers.

    Driver
    Version
    Example URL
    JavaDB Derby 10.4.1.3 jdbc:derby://localhost:1527/sample (Network)
    Oracle Oracle Database 10g Release 2 (10.2.0.2) jdbc:oracle:thin:@//localhost:1521:ora9i
    PostgreSQL 8.3 Build 603 jdbc:postgresql://jsmith.mycompany.com:5432/postgres
    MySQL MySQL Connector/J 5.1.6 jdbc:mysql://localhost:3306/sample
  • Other Drivers

    The following drivers and databases have not been formally tested, but should work based on experience.

    Driver
    Version
    Example URL
    Microsoft Microsoft SQL Server 2005 JDBC Driver 1.2.2828.100 jdbc:sqlserver://localhost:1433;databaseName=travel;selectMethod=cursor
    IBM Redistributable DB2 JDBC Type 4 driver v8 fixpack 13
    jdbc:db2://localhost:50002/sample
    jTDS jTDS 1.2.1 jdbc:jtds:sqlserver://test-mycompany.com:1433/travel
    DataDirect DataDirect Connect for JDBC - 3.6
    DataDirect Connect for JDBC - 3.6.07
    jdbc:datadirect:oracle://localhost;SID=ora9i
    jdbc:datadirect:sqlserver://localhost:1433;DatabaseName=travel;SelectMethod=cursor
    jdbc:datadirect:db2://localhost:50002;databaseName=sample
    Pointbase 5.2 ECF build 294

     

    jdbc:pointbase://localhost:29092/sample

     

 

top


Known Issues: Installer

The unresolved installer issues for this release are as follows:

  • Issue #6720021: Installer doesn't work when using OpenSolaris with any version of JDK 5.

    Description: Installer doesn't work when using OpenSolaris with any version of JDK 5.

    Workaround: Install with JDK 6 or execute the "export AWT_TOOLKIT=XToolkit" command before running the installer using JDK 5.

  • Issue #93568: On Solaris and Linux, installation hangs when the network connection is lost.

    Description: On Solaris and Linux platforms, if the network connection is lost, installation hangs when the installer is searching for a compatible JDK in network directories.

    Workaround: Restore the network connection and proceed with the installation.

  • Issue #117172: A blank window when running the installer on Ubuntu.

    Description: The installer appears as the blank/grey dialog when running on Ubuntu with Beryl/Compiz/Compiz Fusion
    installed.

    Workaround: Execute the export AWT_TOOLKIT=MToolkit command before running the installer.

  • Issue #119861, Issue #117334: Installation stops with error when the unpack200 command is executed.

    Description: Installation stops with error during execution of the unpack200 command. This error can be caused by the Logitech Process Monitor (Webcam Effects Helper) application.

    Workaround: If you have Logitech Process Monitor (Webcam Effects Helper) application (LVPrcSrv.exe) that is running on your system, switch it off before installation or uninstall

  • Issue #122030, Issue #130368: On Fedora Core 8 and Ubuntu 8.04 alpha 6, installation fails when JDK 7 is used.

    Description: On Fedora Core 8 and Ubuntu 8.04 alpha 6, installation of GlassFish V2 fails when JDK 7 is used (JDK7 IcedTea 64-Bit Server VM).

    Workaround: For these platforms, use JDK 5 or JDK 6.

  • Issue #123300. On Fedora Core 8 the installer stops displaying the interface and returns to the console.

    Description: On Fedora Core 8, displaying the installation interface stops and the system returns to the console.

    Workaround: See https://netbeans.org/servlets/ReadMsg?list=nbusers&msgNo=98765.

  • The NetBeans IDE 6.5 Download page can be displayed in the language selected from the Choose Page Language drop-down list.

    Description: The Download page is displayed in the language which is specified as default for the used browser. If you are using a non-localized browser, it will be displayed in English. To view the Download page in Chinese, Japanese, or Brazilian Portuguese, select the relevant language from the Choose Page Language drop-down list at the top of the Download page.

    Workaround: The localized Chinese, Japanese, and Brazilian Portuguese versions of the Firefox browser allow opening a localized Download page. To view the Download page in Chinese, Japanese, or Brazilian Portuguese, select the relevant language from the Choose Page Language drop-down list at the top of the Download page.

  • The NetBeans IDE 6.5 installation wizard does not start properly (hangs). After the user stops the installation process manually, and the installer reports that another installer instance is running.

    Description: On Windows, when Java6 is used by default and large zip files are stored on the desktop, the installation wizard does not start properly (hangs). After the user stops the installation process manually, and the installer reports that another installer instance is running.

    Workaround: Before the installation, remove all big zip files from the desktop

top


Known Issues: Core IDE

The unresolved issues for this release are as follows:

  • Difficulties starting the IDE (Solaris x86 and Dual-Core Opteron).

    Description: On certain Solaris x86 and Dual Core Opteron configurations, you may encounter problems starting the IDE due to a JDK bug with loading GTK look&feel libraries.

    Workaround: If you encounter this behavior, specify the following command line option: -laf javax.swing.plaf.metal.MetalLookAndFeel

  • Characters do not display properly in some Asian locales.

    Description: When running the IDE with some Asian locales on Ubuntu and some other Linux distributions, the IDE's screen text may become unreadable. On certain Linux distributions multi-byte characters may display as a rectangle due to JDK font setting issues.

    Workaround: Because there is no known workaround for this issue, it is recommended to use an alternative Linux distribution if you must use a locale subject to this behavior.

  • Issue #154624: Numerous problems reported when using JDK 6 Update 12 with the IDE.

    Description: A wide range of problems occur when using the IDE with JDK 6 Update 12.

    Workaround: Use JDK 6 Update 11 with the IDE.

  • Issue #6720021: Difficulties starting the IDE on OpenSolaris using any version of JDK 5.

    Description: IDE may not start on OpenSolaris when using any version of JDK 5.

    Workaround: Use JDK 6 or execute the export AWT_TOOLKIT=XToolkit command before starting the IDE.

  • Issue #64840: Network communication broken on Linux with IPv6 enabled.

    Description: Network communication broken on Linux with IPv6 enabled, preventing the IDE from connecting to bundled servers, Auto Update, etc.

    Workaround: If this happens, run the IDE using the -J-Djava.net.preferIPv4Stack=true' switch. Alternatively, disable IPv6 (in /etc/modules.conf or /etc/modprobe.conf).

    For more information see: Issue #5087907.

  • Issue #62919: Profiled application can crash when taking a memory snapshot.

    Description:When profiling an application, the profiled application may crash when you attempt to take a memory snapshot.

    Workaround: Start the application you want to profile with the -Xnoclassgc switch.

  • Issue #110074: Editor periodically freezes on Solaris.

    Description: When running the IDE on Solaris with JDK 6, 6u1 or 6u2, threads may become blocked for a long time and cause the editor to be unresponsive.

    Workaround: Upgrade your JDK 6 installation to Update 3 or newer.

  • Issue #88776: Profiled application can crash when profiling using dynamic attach mode.

    Description:When running on JDK 1.6, profiling an application with dynamic attach mode can lead to the profiled application crashing.

    Workaround: Start the application you want to profile with the -Xshare:off switch.

    Also see: Issue #113847.

  • JDK 6 Issue #6389282: Java applications created from the Java Desktop Application project template might not run under Chinese and Japanese on Linux when using JDK 6.

    Description: Java applications created from the Java Desktop Application project template might not be able to be run in Japanese and Chinese Linux locales with JDK 6 installed.

    Workaround: Use JDK 5.0 or run projects from English locale.

  • Issue #119617: Cursor lost in editor and cannot type using keyboard

    Description: It can sometimes occur that after using a hint in the editor window that the insertion point in the editor disappears and you cannot type using the keyboard. This has mostly been reported on Mac OS X 10.4, but there have been some reports on some versions of Ubuntu.

    Workaround: Use the mouse to open and then close a dialog window (for example, a properties dialog). This returns the focus to the editor and the insertion point and keyboard will work as normal.

  • Issue #119567: Desktop database application project does not run if non-ASCII is in the name of the project or the path to that project.

    Description: The cause is in the current toplink libraries used in the IDE. An issue on toplink library has been filed on it. This Glassfish issue has been fixed for Glassfish v2.1. However, NetBeans 6.5 supports glassfish v2 u2, and the fix is not in this version of Glassfish.

    Workaround: Use only ASCII characters in the name of a desktop database application project or the path to that project.

  • Issue #118174 and other related issues: I18N - Javadoc not found on Solaris, maybe other platforms, in certain cases using the Firefox web brower

    Description: When using Firefox on Solaris, and sometimes on Mac OS and Windows, if multibyte or non-ascii characters are used in project name or path, and if the project encoding property is not set to utf-8 (which means these paths are in that encoding), the generated javadoc is not found or shown.

    For example: In the case of a project that has euc-jp as its project encoding property on Solaris, and has project name or path using Japanese characters of that encoding, the javadoc won't be found and an error message is displayed in Firefox.

    The problem is that part of the URL is UTF-8 and part is EUC-JP; the javadoc tool stores the URL in the encoding it generates for the web page, but the correct way is to generate the text in requested encoding (in this case EUC-JP) and URLs in UTF-8.

    Workaround: Avoid using multibyte in the name of the project or the path to the project.

  • Issue #130357: I18N - Mac OS won't generate javadoc if project name or path has multibyte

    Description: The javadoc task while creating the temporary parameter file is written in default OS encoding which is MacRoman. This appears to be a Mac OS situation where the BSD and Mach parts (system & kernel calls) accept parameters in UTF-8, but OS and HFS promote themselves as MacRoman.

    Workaround: Avoid using multibyte in the name of the project or the path to the project.

  • Issue #130311: On Mac OS, some messages or strings in another language or character set are not shown in output window correctly

    Description: For example, on Mac OS X 10.4. when using System.out.println in the Java code,the strings containing Japanese characters display correctly in the source code, but are displayed as question marks in the output window.

    Workaround: There is no workaround at this time.

  • Issue #152916: Difficulties starting IDE on 64-bit Mac OS X 10.5.5 using JDK 1.6_07

    Description: On certain 64-bit Mac OS X 10.5.5 configurations with JDK 1.6_07 set as the system's default Java platform, you may encounter problems starting the IDE from the Finder and from the command line.

    Workaround: Switch system default to JDK 1.5.

  • Issue #144388: Add Argument for Standalone MySQL Server Installation

    Description: If a user uses a standalone MySQL server with the IDE, no output is displayed in the Output window of the IDE.

    Workaround: Add the argument --console to the list of arguments to start the server.

  • Issue #144398: SQL CC: CC doesn't appear for MySQL system tables

    Description: After executing select * from information_schema.statistics; and then select * from followed by Ctrl+Space, no system table appears in the CC list.

    Workaround: Use the Connector/J Driver in MySQL 5.1.7.

  • Issue #150416: Sample DB can't be created without InnoDB

    Description: Sample database in NetBeans use foreign keys. The MyISAM engine doesn't support foreign keys. Therefore, sample databases cannot be used without the InnoDB storage engine.

    Workaround: Install the InnoDB transactional storage engine.

top


Known Issues: Web and Java EE

The unresolved Web and Java EE issues for this release are as follows:

  • Visual Web JSF Backwards Compatibility Kit
    Description: The Visual Web JSF Backwards Compatibility kit provides supplemental libraries that are required by the Visual Web designer to support projects that are based on J2SE 1.4 or J2EE 1.4. These libraries are not open source and are therefore distributed as a separate NetBeans plugin. The kit will install the following libraries that are required for J2EE 1.4 projects:
    • JavaServer Faces 1.1 Reference Implementation (RI)
    • Rowset Reference Implementation (RI)
    • JAX-RPC libraries from JWSDP 1.6

    To get the Backwards Compatibility Kit, in the main menu, choose Tools > Plugins.

  • Woodstock 4.1 and 4.2 JSF Components Release Notes
    Description: Woodstock 4.1 and 4.2 JSF Components Release Notes are located on the Project Woodstock web site, at http://java.net/projects/woodstock. The build shipped with NetBeans IDE 6.5 is Woodstock 4.2 Build 3.
  • No Support for Ajax Sample Components
    Description: Blue Prints Ajax Sample components are not supported in this release because they are based on a old version of Dojo that is no longer compatible with later versions. Woodstock components bundled in NetBeans depends on more recent versions of Dojo APIs for client side rendering. For most of the widely used BP Ajax components (supported in NetBeans 5.5), there is equivalent functionality available from Project woodstock as listed below.
    • Auto Complete - This blog (http://blogs.sun.com/dmitry/entry/creating_autocomplete_entry_field_with ) describes how to achieve similar functionality with components from Project Woodstock library.
    • Pop up Calendar - Project Woodstock includes a Calendar component.
    • Select Value field - Use auto complete instead which has similar functionality but different UI.
    • Progress Bar - Project Woodstock includes a Progress Bar component.
    • Google Map - Planned for future.
    • Rating Component - Planned for future.
    • RichText Editor - Not supported.
  • Issue #113888: Woodstock themes are incompatible with migration of projects from NetBeans IDE 5.5/5.5.1 to NetBeans 6.5. This issue is related to Issue #99063, Missing Body Element switching to new Woodstock theme.

    Description: Projects with custom themes migrated to NetBeans IDE 6.5 will produce Missing Body Element errors.

    Workaround: Manually switch to the default theme before migrating. Custom themes will not work and will need to be rebuilt.

  • Issue 94193: Not possible to edit bean properties in the Outline window or through source packages in the Projects window.

    Description: In NetBeans IDE 6.5, the Add Menu item is disabled in the Navigator window and there is no functionality for editing the properties through source packages.

    Workaround:

    1. Double click SessionBean1 (or other java file) to open the bean in the Java editor.
    2. Manually add the property, such as private String CustomerId;.
    3. Right click on the property and choose Generate Code.
    4. From the Generate popup menu, select Getters and Setters.
    5. In the Generate Getters And Setters dialog for SessionBean1, select your property and press OK.

      Public Getter and Setter methods are inserted after your property.

  • Issue #95022: Resizing of text field and other components does not work.

    Description: Due to a change in Woodstock components, resize handles have been removed from the following Woodstock components: TextField, Text Area,Password Field, Drop Down and List Box. This issue impacts especially projects imported from Java Studio Creator and NetBeans Visual Web Pack 5.5/5.5.1. Resized components may look different from how they looked in previous releases.

    Workaround: For TextField and Text Area components, use the columns and rows attributes, respectively. Drop Down and List Box have been enhanced to include a new width property.

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

    Description: When a button is placed using absolute positioning, its width is incorrect. For example, when NetBeans IDE 6.5 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:

    • 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>
  • Issue #106299: faces-config.xml of Visual Web JSF projects no longer contains the locale section, as in previous versions.

    Description: faces-config.xml used to have the commented section listing how to indicate other locales, with some lines for certain locales as an example. Users must now add these line manually, making sure the name of the locales of interest are in the supported locales section.

    Workaround: Manually add the desired locale to the locale section of the faces.config.xml file. Here is an example of how the code should appear:

    <application>
    <locale-config>
    <default-locale>en</default-locale>
    <supported-locale>desired locale</supported-locale>
    </locale-config>
    </application>

    See also Issue #103085

  • Issue #125965: Null Pointer Exception on drag and drop after closing a Visual Web project close.

    Description: When working with two Visual Web JSF projects, and when closing the second project and returning to the first, may yield an Null Pointer Exception for the first drag and drop.

    Workaround: Press refresh in designer and continue working. If this does not help, it is necessary to restart the IDE.

top


Known Issues: Java ME


NetBeans enables you to develop Java ME based applications for MIDP, CLDC and CDC devices.

The unresolved Java ME issues for this release are as follows:

  • Connected Device Configuration (CDC) application development requires the installation of a CDC platform emulator.

    Description: The Sun Java Toolkit 1.0 for CDC is not bundled with the 6.5 release.

    Workaround: Download the Sun Java Toolkit 1.0 for CDC from the Sun Developer Network. The NetBeans CDC Emulator Platform Setup Guide has instructions for installing this and other SDKs for CDC development.

  • The Java ME module will not run if a directory name, path to the installation directory, or user directory contain non-ASCII characters.

    Description: The Sun Java Wireless Toolkit does not support non-ASCII characters in project paths.

    Workaround: Make sure that your user directory does not contain non-ASCII characters. If it does, change the IDE's default user directory.

  • JDK 6 Issue #6389282: Chinese and Japanese Linux locales with JDK 6 may fail to run projects.

    Description: Java ME projects created in NetBeans can not be run in Japanese and Chinese Linux locales with JDK 6 installed.

    Workaround: Use JDK 5.0 or run projects from English locale.

  • NetBeans Issue #139031: Emulator does not start in Windows if the Java binary is not in the environment path.

    Description: Sun Java Wireless Toolkit and other emulators do not launch in Windows if Java.exe is not in the path.

    Workaround: Install the JDK using the default settings or, if performing a custom install, be sure to select the public JRE for installation. If the JDK is already installed you can add the Java.exe file to your system's path settings.

top


Known Issues: SOA


This NetBeans SOA 6.5 release lets you explore and evaluate new functionality in the IDE. We encourage you to get involved and give us feedback by logging any issues you encounter in the Issue Tracking system at https://netbeans.org/community/issues.html.

The unresolved SOA issues for this release are as follows:

  • To use the Sun Java System Access Manager, you must install the full download of the IDE, and install Java Application Platform SDK Update 3 Beta or later from http://java.sun.com/javaee/downloads/index.jsp.
  • Issue #114171: WSDL files manually edited by CASA throw Null Pointer Exception in the build.xml output.

    Description: CASA does not support user editing of its generated files, and provides no warning when a user does so.

    Workaround: Do not edit CASA-generated WSDL files. Manual editing of WSDL file is not supported and will cause unexpected results.

  • Issue #84622: IDE does not roll back the retrieval of the WSDL file(s) after you cancel the PartnerLink dialog.

    Description: If you cancel the PartnerLink dialog that appears when you drag a WSDL file or a Web Service node from a NetBeans project onto a diagram, the IDE does not roll back the retrieval of the WSDL files(s).

    Workaround: If these files are not needed by the project, simply delete them manually from the Projects window, as you would delete any other project resource.

  • Issue #112344: Drag and Drop in the tree view of XML schema editor may throw exceptions.

    Workaround: Use JDK 1.6.0_02 or later.

  • Issue #96237: The XSLT Designer does not support messages defined on complex, simple, or built-in types.

    Description: In this release, the XSLT Designer does not support messages declared in WSDL using the type="..." attribute. Only the declarations with the element="..." attribute are supported.

top


Known Issues: C/C++


NetBeans 6.5 C/C++ support C and C++ applications on Microsoft Windows, Macintosh OS X, Linux, and the SolarisTM Operating System. C/C++ developers can bring existing applications into the NetBeans project system, or develop new applications and libraries. NetBeans C/C++ support covers the end-to-end development cycle: projects and templates, an advanced language-aware editor, makefile-based builds, and debugging.

For information on installing and configuring the compilers and tools for NetBeans C/C++ support, see Installing and Configuring C/C++ Support.

The unresolved C/C++ issues for this release are as follows:

  • Issue # 151761: gdb confused on line breakpoints for files with embedded spaces

    Description: If you try to set a line breakpoint with an absolute path with embedded spaces, the command fails.

  • Issue # 149736: Breakpoints do not work on Mac OS X if Output window is used

    Description: On Mac OS X, if you set a line breakpoint, set the Console Type to Output window, and then start the debugger, the debugger starts but does not stop the program at the breakpoint and gets into an "unknown" state. You can end the debugging session by clicking the Finisher Debugger Session button.

    Workaround: Use the External Terminal console type.

  • Issue # 149053: On Windows platforms, the path to make tools cannot contain spaces

    Description: On Windows platforms, if the path to make tools contains embedded spaces, the path is truncated and the tools are not found.

  • Issue # 150099: On Windows platforms, cleaning and building might corrupt a project

    Description: On Windows platforms, executing a Clean and Build on a project in which paths to include files are stored as absolute causes the project to become corrupted.

  • Issue # 148204: On Windows platforms, user input does not work in Output window when debugging

    Description: On Windows platforms, when you are debugging an application and the console type for the project is set to Output Window, you cannot type input in the Output window. This issue does not affect development using a remote host.

    Workaround: Set the console type to External Terminal by right-clicking the project node in the Projects window, selecting the Run node in the Project Properties dialog box, selecting External Terminal from the Console Type drop-down list, and clicking OK.

  • Issue # 151610: On Windows platforms, debugger cannot attach to a project built with MinGW

    Description: On Windows platforms, when you build a project with MinGW tools. run the application in the IDE, and try to attach the debugger to the running process, the Attach dialog box contains only /usr/bin/ps.

  • Issue # 121776: Sun Studio compiled code sometimes has problems being debugged with gdb

    Description: On the Solaris and Linux operating systems, code compiled with the Sun Studio compilers cannot always be correctly debugged with the gdb debugger. Most known problems are fixed in the Sun Studio 12 software but several more exist. If you run into problems debugging programs compiled with Sun Studio 12 compilers, the first thing you should do is apply the latest Sun Studio 12 product patches. If your problem still exists, please file a defect in Issuezilla and make this task depend on it.

    As problems are found, we will open new issues and update this task to depend on them, giving some idea of the current state of debugging programs compiled with Sun Studio 12 compilers using NetBeans and the gdb debugger.

    These problems do not affect debugging code compiled with Sun Studio 12 compilers using the Sun Studio 12 IDE and the dbx debugger.

  • Issue #121775: Need latest Xcode for debugging on Tiger (Mac OS X 10.4)

    Description: When debugging on the Macintosh with Tiger (Mac OS X 10.4), the default version of the gcc and g++ compilers generates code with a bug in the debug output. Apple has released an updated Xcode package (version 2.5) with a fix for this problem. The correct versions of gcc, g++, and gdb are:

    gcc: 4.0.1 - Apple build 5367
    g++: 4.0.1 - Apple build 5367
    gdb: 6.3.50 - Apple build 573 (10/20/2006)

    To download this version of Xcode, see http://developer.apple.com/tools/download.

    This problem is not an issue on Leopard (Mac OS X 10.5).

    The symptoms of the problem are that executables compiled with the -gdwarf flag (the default for C/C++ application projects) have incorrect line information and breakpoints may be ignored.

top

More Information


You can find news, articles, additional modules, and other useful information on the NetBeans project web site. Since NetBeans is an open-source project, the web site also provides access to source code, a bug database, information on creating your own NetBeans modules, and much more. For more information, visit http://www.netbeans.org.

Documentation

To get the most out of the new functionality in NetBeans IDE 6.5, check out the continuing series of web-based tutorials and screencasts. Keep checking these pages, as we are adding new content all the time.

The built-in help system for NetBeans IDE 6.5 has been updated to reflect the changes in the user interface since release 6.1.


Community

You can keep up to date on the the latest developments and interact with the NetBeans community by signing up for NetBeans project mailing lists at https://netbeans.org/community/lists/.

You can also post your questions at http://forums.netbeans.org/ which are synchronized with the most widely used NetBeans mailing lists. Note that a separate sign up for the forums is required.


top


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo