Java EE 5 Tools Bundle Release Notes

Java EE 5 Tools Bundle Release Notes


October 2006  [Revision number: V1-0]


The Java Platform, Enterprise Edition 5 (Java EE 5) Tools Bundle includes NetBeans IDE 5.5, NetBeans Enterprise Pack 5.5, and Java Platform, Enterprise Edition 5 SDK Update 1 or Update 2 (Java EE 5 SDK Update 1 or Update 2). The NetBeans Enterprise Pack 5.5 includes XML schema tools modules, BPEL modules, Secure Web Services modules, Project Open ESB Starter Kit, Sun Java System Access Manager 7.1, and Sun Java System Policy Agent 2.2 for Sun Java System Application Server 9.0 Update 1/ Web Services.
These release notes apply to the Java EE 5 Tools Bundle.

Note: The UML functionality is no longer available in the final (FCS) release of the NetBeans Enterprise Pack 5.5 download. Instead, the UML functionality is offered separately on the Auto Update Center.

Contents

 
System Requirements
Configuration Information
Limitations
Known Issues
 

Note: If you are looking for information about installing the software included in Java EE 5 Tools Bundle, see the Java EE 5 Tools Bundle Installation Instructions.

System Requirements


Supported Operating Systems

The NetBeans IDE 5.5 runs on operating systems that support the Java VM. Below is a list of platforms that the Java EE 5 Tools Bundle has been tested on.

  • Microsoft Windows XP Professional SP2 or newer
  • Mac OS X 10.4.5 or newer
  • Red Hat Fedora Core 3 (except when running in the zh_CN locale and possibly other Asian locales)
  • Solaris 10 Operating System (Solaris OS) 7/05 (SPARC® and x86/x64 Platform Edition)

NetBeans Enterprise Pack also runs on the following platforms:

  • Microsoft Windows 2000 Professional SP4
  • Solaris 8 OS (SPARC and x86/x64 Platform Edition) and Solaris 9 OS (SPARC and x86/x64 Platform Edition)
  • Various other Linux distributions

Minimum Hardware Configuration

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

  • Microsoft Windows operating systems:
    • Processor: 500 MHz Intel Pentium III workstation or equivalent
    • Memory: 512 MB
    • Disk space: 850 MB of free disk space
  • Linux operating system:
    • Processor: 500 MHz Intel Pentium III workstation or equivalent
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space
  • Solaris OS (SPARC):
    • Processor: UltraSPARC II 450 MHz
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space
  • Solaris OS (x86/x64 Platform Edition):
    • Processor: AMD Opteron 100 Series 1.8 GHz
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space
  • Macintosh OS X operating system:
    • Processor: PowerPC G4
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space

Recommended Hardware Configuration

  • Microsoft Windows operating systems:
    • Processor: 1.4 GHz Intel Pentium III workstation or equivalent
    • Memory: 1 GB
    • Disk space: 1 GB of free disk space
  • Linux operating system:
    • Processor: 1.4 GHz Intel Pentium III or equivalent
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space
  • Solaris™ OS (SPARC®):
    • Processor: UltraSPARC IIIi 1 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space
  • Solaris™ OS (x86/x64 platform edition):
    • Processor: AMD Opteron 100 Series 1.8 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space
  • Macintosh OS X operating system:
    • Processor: PowerPC G5
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

Required Software

NetBeans IDE 5.5 runs on the Java SE Development Kit 5.0 Update 9 or higher (JDK 5.0, version 1.5.0_09 or higher), which consists of the Java Runtime Environment plus developer tools for compiling, debugging, and running applications written in the Java language. Sun Java System Application Server Platform Edition 9 Update 1 has been tested with JDK 5.0 update 6.

  • For Solaris, Windows, and Linux, you can download the JDK for your platform from here
  • For Mac OS X, the Java SE Development Kit 5.0 Release 4, is required. You can download the JDK from Apple's Developer Connection site. Start here: http://developer.apple.com/java (you must register to download the JDK).

Sun Java System Application Server Requirements

In order to use the J2EE development features of the Java EE 5 Tools Bundle, you must have Sun Java System Application Server Platform Edition 9 Update 1. This Application Server is bundled with the Java EE 5 Tools Bundle download.

Configuration Information


This topic provides configuration information that you may need in order to configure the software.

Sun Java System Application Server

The default username and password values for the default Application Server domain, domain1, are as follows:
username: admin
password: adminadmin

Sun Java System Access Manager

If you need to access the administration console for the Access Manager server, use the following values:
username: amadmin
password: admin123

Limitations


Limitations in this NetBeans Enterprise Pack 5.5 release are as follows:

  • Editing of web service client's security attributes used by a jsp within Java EE 5 web applications is not supported.
  • Liberty token profile is not supported for Java EE5 web services.
  • The NetBeans Enterprise Pack 5.5 composite application test run feature uses the system classpath. This may result in test run failures due to incompatible jar file inclusion.
  • BPEL validation is not started automatically after you modify WSDL files.
  • The Exit, OnMessage, Receive, and OnEvent elements are not fully supported or have restricted usage in this release of the BPEL Designer.
    See the BPEL 2.0 Elements Not Present in This Release section of the Developer Guide to BPEL Designer for the complete list of BPEL 2.0 elements and attributes that are not present in this release of the BPEL Designer.
  • The OnAlarm event handler of the Repeat Every type breaks execution of the BPEL process.
  • Some of the runtime components, namely Sun Java System Application Server 9 PE Update 1, Samples and BluePrints, are not localized on the MacOS X operating system.

Known Issues


This Java EE 5 Tools Bundle lets you explore and evaluate new functionality in the IDE. We encourage you to send us feedback by logging any issues you encounter in the Issue Tracking system at http://www.netbeans.org/community/issues.html.

Note: Refer to NetBeans IDE 5.5 Release Notes for the list of issues specific to the IDE.

The unresolved issues for this release are as follows:

Installation

  • Installer fails to start correctly with little or no free disk space in the temp directory.

    Description: On Microsoft Windows, if your system is set up to use a temporary directory on your C drive, and that temporary directory does not have enough space for the temporary files needed by the installer, the installer will report that there is not enough disk space on the C drive. This is the case even if you chose to install to a different drive. The installer is in fact reporting that it needs additional temporary space.
    The issue exists in the InstallShield framework.

    Workaround: Start the installer with the -is:tempdir custom-temp-dir command line parameter. The custom-temp-dir should contain at least 130 MB of free disk space.

  • NoClassDefFoundError: cannot access amserver occurs during installation.

    Description: If you try to install the software a second time without cleaning up the Access Manager directory, the configuration of Access Manager may fail during installation.

    Workaround:

    • On Microsoft Windows:
      Delete the directory specified in: %SystemDrive%\Documents and Settings\ user-name\AMConfig_server_amserver_ and then remove the file %SystemDrive%\Documents and Settings\ user-name\AMConfig_server_amserver_ .
    • On UNIX/Mac OS X:
      Delete the directory specified in: $HOME\AMConfig_server_amserver_ and then remove the file $HOME\AMConfig_server_amserver_ .
  • Installer fails when using the -console and -silent options.

    Description: On UNIX platforms, if the installer cannot run the installation process without the graphics mode, the installer suggests that you run it using the -console and -silent options. If you try this, the installer fails.

    Workaround: Ignore the message from the installer and set up the GUI environment as described below to proceed with the installation.
    The most common cause for this issue is that you are connecting to the target system via telnet/ssh/rlogin, which means you must redirect the GUI to the originating system. To do this successfully, the following two requirements must be met:

    1. An X server should be set up and running on the system from which you are connecting.
    2. The DISPLAY environment variable should be set to the correct value on the target system. Assuming a bash shell, the correct value and command for the variable are:
      export DISPLAY= machine-name: display-number
      Where machine-name is the IP address of the system from where you are connecting, and display-number is the number of the display, usually 0.0.
  • Installation fails after manual uninstallation.

    Description: If you try to install the product after performing a manual uninstallation by deleting files, the installation will fail because the data in InstallShield's VPD registry is not cleaned up.

    Workaround: Before starting a new installation, remove the InstallShield VPD registry. This registry resides on Microsoft Windows in %SystemDrive%\Program Files\Common Files\InstallShield\Universal or on Linux/Solaris/Mac OS X in ~/InstallShield.

    Note that other applications (for example, NetBeans IDE) can use the InstallShield VPD registry to store their uninstallation data. The InstallShield VPD registry removal prevents such applications from correct uninstallation. It is strongly advised to uninstall applications that use the InstallShield Universal installer engine prior to removing the VPD registry.

  • On Mac OS, cannot double-click installer to start installation.

    Description: On Mac OS, if the default java version on your system is 1.4, you will not be able to double-click the .jar file to start the installation.

    Workaround: Run the .jar file manually from the command line using java 1.5.

  • Installer exceptions when running on JRE 1.4.

    Description: On Microsoft Windows, if there is no preinstalled compatible JDK on the target machine, the InstallShield Windows launcher allows you to select a custom java.exe. After you select a custom java.exe, the installer does not perform a validation for compatibility. This means that if you select a java.exe from a 1.4 JRE which is not compatible with the installer, you will encounter a number of exceptions. The issue exists in the InstallShield framework.

    Workaround: Select a java.exe from a 1.5 JRE. See Required Software for information about downloading and installing a compatible JDK.

  • Installer fails to start correctly on UNIX.

    Description: The installer fails to start correctly on UNIX when is there is little or no disk space in the root directory of the file system. The problem exists in the InstallShield framework. This issue was observed on machines with less than 2.5 MB free in the root of the file system.

    Workaround: Free up enough disk space in the root of the file system and restart the installer.

  • Repaint problems on MacOS X with JDK 1.6.

    Description: When dragging a tab, a black square area is being dragged. After you drop the tab problems with the Welcome screen repainting appear.

    Workaround: Set -J-Dapple.awt.graphics.UseQuartz=true or use Java 1.5 for running the IDE (or _select_ Java 1.5 during the NetBeans Enterprise Pack installation).

BPEL

  • WSDL model cannot resolve portType.

    Description: The WSDL model cannot resolve portType when the main and imported WSDL have the same targetNamespace.

    Workaround: Assign a namespace for the imported WSDL file, distinct from the namespace of the importing WSDL file.

  • Mapper is not refreshed after adding a new element in an XML schema file.

    Description: The BPEL Mapper is not refreshed after adding a new element in an XSD file.

    Workaround: Close and reopen the Mapper window.

  • Generation and validation bug when importing WSDL files.

    Description: Import of a WSDL file into another WSDL file is not validated. Corresponding error message displays.

    Workaround: Go to the Source view of the WSDL Editor, remove the import and namespace that have just been added. Go to the tree mode of the WSDL view, and add the same import again.

  • Mix of prefixed and non-prefixed expressions when editing an older version of the BPEL tool.

    Description: Today all xpath expressions created in the BPEL tool have a namespace prefix. In all prior versions of the tool xpath expressions were not prefixed with namespace. If you edit an older BPEL (created with an older version of the tool) and add new assigns to it, you will get a mix of prefixed and non-prefixed expressions since the engine cannot handle this mix. The following combination of problems may occur:

    • You may not get the expected result because the non-prefixed expressions may not return a result.
    • You may get an exception because the code expects a result to be returned and due to the missing prefix no results are returned.

    Workaround: Manually edit non-prefixed expressions to add a prefix.

  • BPEL Service Engine "Unexpected Reply Activity Encountered" errors during JBI Longevity test run.

    Description: The Unexpected Reply Activity Encountered. Possible Cause: Potential multiple reply activities for given receive activity. server-side error occurs when running the benchmark project in a multi-thread environment, that is:

    • The BPEL-SE is configured with more than 1 thread (default is 10 threads)
    • The BPEL-SE is running on a multi-processor machine (might occur on a very powerful single CPU machine too)

    This problem can occur in any business process which receives a fault from another business process or an external web service and is running in a multi-threaded environment.
    Since the benchmark project has a business process which receives a fault from another business process, this error displays while running the longetivity test.
    The issue reproduces on Solaris and Windows.

    Workaround: Change the benchmark project so that the business processes do not communincate using faults, but rather using normal replies.

  • BPEL processes continue running after test execution is completed.

    Description: Currently runtime does not support time-outs for a process execution. This makes a business process wait for a certain event for unlimited time.

    Workaround: Consider using Pick activities with onAlarm branches where applicable.

  • Tests fail for BluePrint4Application project.

    Description: After deploying the BluePrint4Application project to the application server, the sample tests will fail if not run in a specific order. This is caused by the use of correlation in the BluePrint 4 BPEL processes.

    Workaround: Run the BluePrint4Application tests in any order specified below:

    • poServiceRequest -> poRequestCancel
    • poServiceRequest -> poRequestConfirm


  • IDE does not roll back the retrieval of the WSDL files(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.

  • Deleting a property from a correlation set in the Navigator incorrectly deletes the property from WSDL.

    Description: If you delete a property from a correlation set using pop-up menu commands in the Navigator, the property is incorrectly deleted from the WSDL file.

    Workaround: Use the correlation set property editor to delete a property from a correlation set correctly.

  • BPEL process hangs if the interface of a partner service changes.

    Description: If the interface of your partner service changes, for example, when the signature of a web service operation changes, and you have not imported the modified WSDL file, then the BPEL process hangs.

    Workaround: Import the new WSDL file and redeploy the application. The BPEL service engine restart may require.

  • Unable to Show Diagram message when the BPEL file is well formed.

    Description: The Unable to Show Diagram message displays although the BPEL file is well-formed.

    Workaround: Restart the IDE.

  • Invoking actions from Navigator for broken BPEL may lead to exceptions and IDE hang.

    Description: Invoking actions from the Navigator for a broken BPEL may lead to exceptions thrown or the IDE hang.

    Workaround: All actions should be disabled from the Navigator when BPEL is broken. Do not invoke actions for a broken BPEL from the Navigator. Correct the BPEL first.

  • On UNIX, editing of the string literal INPUT text field is sometimes unavailable.

    Description: On UNIX, after double-clicking the text field in the string literal box changes to the edit mode for a second and then goes back to the non-edit mode.

    Workaround: Double-click the text field in the string literal box, then click a white place inside the BPEL Mapper editor field quickly (before it turns back to the non-edit mode). The string literal box will stay in the edit mode.

  • NetBeans Visual Web Pack 5.5 breaks the drag and drop functionality in NetBeans Enterprise Pack 5.5 BPEL/SOA projects.

    Description: NetBeans Visual Web Pack 5.5 breaks the drag and drop functionality in NetBeans Enterprise Pack 5.5 BPEL/SOA projects.

    Workaround: Choose Tools > Update Center from the main NetBeans IDE menu to launch the Update Center Wizard. Install Update 1 for NetBeans Visual Web Pack 5.5 final release via the Update Center.

    Note that though Update 1 is visible for the NetBeans Visual Web Pack 5.5 Technology Preview users, you need to uninstall the Technology Preview release and download and install the final release of the NetBeans Visual Web Pack 5.5 from the NetBeans Visual Web Pack 5.5 Download page for the Update 1 to take effect.

Secure Web Services

 

  • Execution of secure web services enabled application with liberty profile fails if the URL is "localhost"-based.

    Description: Execution of secure web services enabled application with liberty profile fails if the URL is "localhost"-based. When the Run project is invoked from the IDE, the default URL generated by the IDE includes localhost.

    Workaround: Access the stockclient from the browser with the hostname that does not include the localhost name.

  • J2EE 1.4 web applications bundled in an EAR and secured with Liberty token profile require manual adding of the security role mapping.

     

    Description: If you add Liberty Token Profile secured J2EE modules to the Enterprise Application project, the roles added to the J2EE modules need to be manually added in the Enterprise Application for end-to-end security to work.

    Workaround: Manually add the lines below to the EnterpriseApplication->Configuration Files->sun-application.xml file using the xml text editor.

    <security-role-mapping>
            <role-name>AUTHENTICATED_USERS</role-name>
            <principal-name>AUTHENTICATED_USERS</principal-name>
    </security-role-mapping> 
    


  • Editing of Access Manager profiles may be unavailable if system proxy settings are used in the IDE.

    Description: On Windows, the NetBeans Enterprise Pack 5.5 uses the proxy settings for the Internet Explorer as the system proxy settings. This may cause the connection failure and makes editing of Access Manager profiles unavailable if the IE's proxy settings are incorrect.

    Workaround: Set up your own proxy settings in the IDE. Open Tools > Options dialog, switch to HTTP Proxy and enter the correct proxy settings.

  • Liberty registration fails during WSP deployment on a remote system if system clock settings differ.

    Description: This is an Access Manager feature. There is a setting in AMConfig.properties for a timeout limit on response from discovery service. The registration request is rejected as an "old message" due to the time difference between the system clocks.

    Workaround: Put the system clocks in synch.

  • Access Manager is not supported for Java version 1.6.

    Description: Access Manager is not supported for Java version 1.6.

    Workaround: Use Java 1.5.x to run the Access Manager.

  • Issues with AM configurator and the installer with respect to AMConfig.properties.

    Description: If the Access Manager server configuration is changed after an installation, the AMConfig.properties file does not get modified to reflect the changes. This can cause discrepancies between the configured Access Manager server and the AMConfig.properties file resulting in the IDE not being able to talk to the Access Manager server via the client SDK.

    Workaround: Manually sync up the client's AMConfig.properties file to reflect the proper Access Manager server information.

XML Schema Tools

  • Deleting multi selected nodes sometimes fails in column view.

    Description: When using the column view, sometimes only one of the multi selected nodes is removed after the Delete command from the pop-up menu is invoked on them .

    Workaround: Multi select and use the Delete key, or sequentially single select and choose Delete from the context menu, or use the Tree Editor.

XML Schema Tools, BPEL, and Secure Web Services Modules

The issues described below occur with IDE when using the NetBeans Enterprise Pack 5.5 modules.

  • IDE does not recognize projects created under root directory "/".

    Description: On Mac OS X, Solaris, and Linux, the IDE does not recognize projects created under root directory "/".

    Workaround: Create projects in a folder.

  • Characters do not display properly in some Asian locales.

    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.

See Also:


Rate and Review
Tell us what you think of the content of this page.
Excellent   Good   Fair   Poor  
Comments:
If you would like a reply to your comment, please submit your email address:
Note: We may not respond to all submitted comments.
 
Left Curve
Java SDKs and Tools
Right Curve
Left Curve
Java Resources
Right Curve