Sun Java™ Studio Enterprise 8.1 Release Notes

Last updated: December 7, 2006

For the latest information on this release of the Sun Java™ Studio Enterprise (Java Studio Enterprise) integrated development environment (IDE), see the Sun Developer Network website at http://developers.sun.com/jsenterprise.

A. What's New

Back to Top

B. System Requirements

Supported Operating Systems

The following table lists the system requirements for installing the Java Studio Enterprise software on any of the supported platforms.

Required Software

Java Studio Enterprise 8.1 requires Java Platform Standard Edition Development Kit (JDK) 5.0 Update 1 or later (32-bit JVM only).

The recommended version is JDK 5.0 Update 7 (the internal version number for this JDK release is 1.5.0_07). Before you start installing the Java Studio Enterprise IDE, make sure that you have at least JDK version 5.0 Update 1 or later installed on your system.

You can download the recommended JDK version for your operating system from http://java.sun.com/j2se/1.5.0/download.jsp

Important: This release of the Java Studio Enterprise software does not support Java™ SE Development Kit (JDK) 6.

Back to Top

C. Platforms

All the components of the Sun Java™ Enterprise System contained in the IDE are for development purposes only. Those licenses cannot be used for commercial use.

Software Platforms

Multi-User Hardware Platforms

Cohabitation

Java Studio Enterprise 8.1 can coexist with Java Studio Enterprise 8, NetBeans™ 5.0, and Sun Java™ Studio Creator 2 on the same system. You do not have to uninstall these tools to install and run Java Studio Enterprise 8.1.

Back to Top

D. Bundled and Supported Software Products

The following tables show the products that are supported by Java Studio Enterprise.

• Java Studio Enterprise supports the UML 2.0 specification. For more information about this specification, see http://www.uml.org/.
• The bundled servers support local configurations. In addition, Sun Java System Application Server and Sun Java System Web Server support remote deployment.

Menu of All Products

Products for Your System

Back to Top

E. Known Issues

This section identifies the most important issues that affect you. This section does not include a complete list of all Java Studio Enterprise bugs. If you have a Sun support contract, you can access a complete list of bugs through the SunSolve^SM Online site at http://sunsolve.sun.com.

This section contains the following topics:

• UML Issues
• WebSphere Plugin Issues
• Other Issues

UML Issues

87610 - When reverse engineering a Java project, template interfaces in nested classes are handled incorrectly.

Description: When reverse engineering a Java project that includes a template interface in a nested class, the resulting UML model does not show the nested class as a template interface.

Workaround: None.

87639 - When reverse engineering a Java project, generic type for attributes, operations, and arguments in nested classes are lost.

Description: The Generic type for attributes, operations, and arguments in nested classes are lost when reverse engineering a Java source code into a UML project.

Workaround: None.

78453 - Drawing a Generalization link to or from an Enumeration element causes incorrect codes to be generated.

Description: It is possible to draw a Generalization link to and from an Enumeration element even though an enumeration can not extend a class in the Java language. Doing so will cause incorrect codes to be generated.

Workaround: None.

87501 - Drawing a Generalization link from an Enumeration element to an Interface element results in empty generated source code.

Description: When drawing a Generalization link from an Enumeration element to an Interface element, no source code is generated for the Enumeration element after Generate Code action is invoked.

Workaround: None.

87841 - Nested classes that have been removed from the source code still appear in the UML model after a Reverse Engineer action.

Description: If a nested class is removed from a Java project and the Java project is reverse-engineered into the same UML project as before, the nested class that was removed still appear in the UML model in the Diagram editor.

Workaround: Close and re-open the diagram in the Diagram editor window.

78312 - UML model report generation is slow on remote desktop.

Description: Generating a model report might take 30 times longer if performed through a remote desktop.

Workaround: To enhance the performance of the UML Modeling feature when it is used on remote systems, add the -J-Dsun.java2d.pmoffscreen=false command-line switch to the default_options statement in the jstudio-installation-directory/ide/etc/jstudio.conf file and then restart the IDE.

78574 - Performance is slow when exporting a diagram to .png format.

Description: Exporting a UML diagram to the .png format could take a long time, and the IDE may seem to be frozen.

Workaround: Same as for Issue 78312.

78505 - UML Modeling performance is slow on a remote desktop when the Overview window is open.

Description: The performance is slow on a remote desktop when working on UML modeling while the Overview window is open.

Workaround: Same as for Issue 78312.

82394 - Diagrams are missing in the report on Linux and Solaris platforms.

Description: When working on Linux or Solaris OS with the display color depth set to 24 or greater, exporting a model diagram to .jpg format results in an empty .jpg file. Diagram images are also missing in the model report when generated.

Workaround: If you are using a Linux system, you probably just ran into issue 4908153. A workaround is to lower your system color depth to 16.

WebSphere Plugin Issues

78910 - Cannot set context path/root for web applications deployed to WebSphere.

Description: After deploying a web application to a WebSphere server instance, its context root always has a value of "/".

Workaround: Deploy the web application from WebSphere Administrative Console, specifying the desired context root:

1. Build the web application, do not try to run the project from the IDE.
2. Launch the WebSphere Administrative Console.
3. From the menu, choose Applications > Install New Application.
4. Specify the path to the web application's archive file and the desired context root.
   The web application's archive file resides in the dist subdirectory of the project's directory.
5. Click Next and follow the instructions of WebSphere.

78911 - Random name is generated for web applications deployed to WebSphere.

Description: After deploying a web application to a WebSphere server instance, it has a randomly generated name.

Workaround: Deploy the web application from WebSphere Administrative Console, specifying the desired application name:

1. Build the web application, do not try to run the project from the IDE.
2. Launch the WebSphere Administrative Console.
3. From the menu, choose Applications > Install New Application.
4. Specify the path to the web application's archive file and the desired context root.
   The web application's archive file resides in the dist subdirectory of the project's directory.
5. In the "Select installation options" window, specify the desired application name.
6. Click Next and follow the WebSphere instructions.

79221 - Cannot refresh the Server Trace Log for WebSphere.

Description: Sometimes WebSphere Server Log in the IDE is refreshed incorrectly.

Workaround: Restart the IDE. You can also use external tools to trace logs.

79505 - The ibm-web-bnd.xmi file is not repainted in the Design view when Binding is deleted.

Description: For ibm-web-bnd.xmi files of enterprise applications, removing a binding is not reflected properly in the Design view.

Workaround: Collapse and expand the surrounding node to see the changes.

84203 - Incorrect message when Run Web Applications fails to start the application.

Description: When running a web application fails for some reason, the output log displays information that the application has been successfully started.

Workaround: Check whether the application was deployed correctly using the WebSphere Administrative Console.

84809 - The ibm-web-bnd.xmi and ibm-ejb-bnd.xmi files do not show up-to-date information.

Description: When the ibm-web-bnd.xmi and ibm-ejb-bnd.xmi files for enterprise applications deployed to a WebSphere server instance are opened in the editor, both XML and Design views do not show the latest changes.

Workaround: Switch to the XML view and back to show the latest changes.

86507 - Debugger does not stop at breakpoints in .jsp files.

Description: For enterprise applications without EJB modules that are targeted to a WebSphere server, the debugger does not stop at breakpoints set in .jsp files.

Workaround: Use breakpoints in servlets.

88995 - Deployment could fail without explicit reasons.

Description: Deployment of web applications, enterprise application or EJB modules project to a WebSphere server sometimes fails without any visible reasons.

Workaround: Follow these steps to deploy an application:

1. Log in to the WebSphere Administrative Console.
2. Examine the list of deployed applications.
3. Start the application if it is currently stopped.
4. (Optional) If this does not help, stop and undeploy your application and then repeat Deploy or Run Project commands in the IDE.

Other Issues

6359947 - InstallShield determines incorrectly the amount of free disk space required to unpack the installer in the temporary directory.

Description: The installer first extracts the required files to the default temporary space directory defined by the TEMP environment variable. If the amount of disk space is less than required, the installation might fail or proceed incorrectly.

Workaround: Specify another temporary directory by starting the installer with the -is:tempdir <path-to-temp-dir> command. The custom temporary directory should have at least 120 MB of free disk space.

6375086 - Installation fails on the Solaris operating system with insufficient disk space in the home directory.

Description: Under Solaris, If the available disk space in the home directory is less than 2.5 MB, installation fails with the following message:

Could not utilize start class: com.installshield.wizard.Wizard

The issue is related to creating a VPD database, which is required for the installer.

Workaround: Provide more free space in the home directory.

6466236 - Exception occurs when invoking refactoring for renaming a package in a Portlet provider application.

Description: When you try to rename a package in a Portlet Provider application using the Refactor > Rename command, an exception occurs.

Workaround: Close the exception dialog box and proceed with refactoring.

6466228 - Packages of Portlet applications cannot be renamed using the Refactor > Rename command.

Description: When renaming the packages of Portlet applications using the the Refactor > Rename command, old package names can remain in .portlet files.

Workaround: Refactor necessary configuration files manually.

6466214 - Debug Project does not perform correct deployment for Portlet Provider Applications.

Description: When using the Debug Project command to debug Portlet Provider Applications (without deploying them first), a debugging session starts with an exception.

Workaround: Deploy or run the project before invoking the Debug Project command.

6485524 - Add All Sub folders command on the project's folder is not working (PVCS).

Description: Adding all subfolders recursively in PVCS profile is not working.

Workaround: Use PVCS command line tools to use "add all" feature.

6471560 - Fail to start the IM server (Collaboration Runtime) if installed with JDK 1.6.

Description: The Collaboration Runtime can not be started on Windows XP, if the IDE is installed with JDK 1.6.

Workaround: Use JDK 1.5.

6498002 - The mouse pointer for the Enterprise Profiler is not refreshed.

Description: Sometimes the mouse pointer for the Enterprise Profiler is not refreshed and its status is displayed as an hour glass for a long time.

Workaround: Follow these steps:

1. Start the Application Server.
2. Enable the Profiler for an application.
3. Run the project.
4. Open the Profiler

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.

Back to Top

F. Modules Available From the Update Center

The IDE's Update Center wizard allows you to update your IDE's installed modules dynamically. When you connect to the Update Center, the IDE checks to see if there are new modules or new versions of already installed modules available. If new or updated modules are available, you can select, download, and install the modules you need.

When you start the Update Center wizard in Java Studio Enterprise 8.1, the Sun Java(TM) Studio Enterprise Update Center and the NetBeans Update Center are selected as the update centers to connect to. You can select any of the other update centers to download and install additional modules.

To support feature compatibility with Sun Java Studio Enterprise 8 and Sun Java Studio Enterprise 7, you can download and install the following modules from the different update centers:

NetBeans Update Center

NetBeans Update Center Beta

Back to Top

G. How To Request Support

Request support and visit the product home page by using the Java Studio Enterprise IDE's Help menu. In the IDE, select Help > Developer Resources and Support to open the product home page in a browser window. On the product home page, open the Support tab and click the Sun Developer Expert Assistance Service link to request technical support or the Discussion Forum link to ask the developer community for assistance.

Back to Top

H. Related Documentation

The following table provides links to Release Notes for products that are bundled or supported with Java Studio Enterprise.

Back to Top

Last updated: December 7, 2006