Sun Java^TM Studio Enterprise 8 Release Notes

For the latest information on this new release of the Sun Java^TM Studio Enterprise (Java Studio Enterprise) integrated development environment (IDE), see the Developer's Resources website at http://developers.sun.com/jsenterprise.

A. What's New

To request an enhancement that is not listed in this section, submit a product request.

B. System Requirements

The following table lists the system requirements for installing an IDE configuration on any of the supported platforms.

• The Windows system disk requires 150MB at C:\WINDOWS\Downloaded Installations\{04842308-B3D2-4584-9F91-DF9D039BF685}.

C. Platforms

The IDE contains all the components of the Sun Java^TM Enterprise System for development purposes only. Those licenses cannot be used for deployment.

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/.
• All bundled servers include local and remote configurations, except that Sun Java System Web Server does not support remote deployment.

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. If you identified an unknown bug, submit a product request.

This section contains the following topics:

• NetBeans Mobility Module
• Localization
• InstallShield
• Deployment to Sun Java System Application Server SE/EE
• Bugs

NetBeans Mobility Module

To install the NetBeans Mobility module on Java Studio Enterprise:

1. Launch the NetBeans Mobility Pack 4.1 Installer.
2. In the NetBeans Mobility Pack 4.1 Installer window add one of the following paths in the NetBeans Installation Directory field:

• Windows: JSE8_INSTALL_DIR\ide
• Unix/Linux: JSE8_INSTALL_DIR/ide

InstallShield

There are problems with InstallShield. For InstallShield bugs, go to Sun Java Studio Enterprise Technical FAQs.

Deployment to Sun Java System Application Server SE/EE

There are problems that might prevent you from deploying to Sun Java System Application Server SE/EE. To ensure a successful deployment, use the information in Using Sun Java Studio Enterprise 8 to Deploy Applications on Sun Java System Application Server 8.1 SE/EE.

Bugs

5097924 I18N - simulator messages do not come from localized bundle files

Description: When you use Portlet Builder's Simulator with Sun Java System Application Server, messages in the Simulator might not originate from localized bundle files.

Workaround: Do one of the following:

• Log into the Simulator as the Japanese or Chinese user. Mao is the Japanese user. Chong is the Chinese user.
• Set the locale of the server instance to that of your locale, or set the locale of the admin server as described in Bug 5108171.

5103318 I18N - J3023 - cant enter double byte chars for attrib/op names in proj tree/edit control

Description: When you use Edit Control to enter double byte characters for attribute and operation names, your changes do not propagate to the model.

Workaround: Change the names of elements, attributes, and operations through the Properties window.

5103320 I18N - J3025 - cant enter more than one double byte character to name classes using edit control

Description: You cannot use the Diagram Editor to apply more than one double-byte character to name classes.

Workaround: Change the names of elements, attributes, and operations through the Properties window.

5108171 I18N - need to set AS admin locale to use packager

Description: When you use Portlet Builder's Packager in another locale with Sun Java System Application Server as your default server, you might see messages displayed as "??" for multibyte characters. This problem does not exist if you use Apache Tomcat as your default server.

Workaround: To use the Packager in another locale and see localized messages displayed properly, manually set the Sun Java System Application Server instance locale. Use the Application Server administration GUI to change the locale. Set the locale to a specific value or leave the locale blank so that the server instance picks up the system locale when the server starts.

6264283 l18N - can't input multibyte into class diagram attributes or operations names

Description: You cannot input multibyte into class diagram attributes or operations names. The problem resides in the the diagram edit control.

Workaround: Change the names of elements, attributes, and operations through the Properties window.

6316501 Application can't be deployed on server without WebSphere-specific custom DDs

Description: You cannot deploy a web application using WebSphere as your server and without WebSphere-specific custom DDs (deployment descriptors).

Workaround: Create and maintain WebSphere-specific custom DDs manually.

6317955 I18N - pasting multibyte into diagram does not show correct multibyte

Description: When you paste multibyte into a diagram, the incorrect multibyte displays in the drawing area.

Workaround: Change the names of elements, attributes, and operations through the Properties window.

6324728 I18N - multibyte does not display ok in deployed web app with one small jsp file

Description: When you create a web application with Sun Java System Web Server 6.1 as the server on which to deploy, and the application has multibyte in the JSP file, when you deploy the application, the multibyte shows as question marks in the browser. Even if you change the browser encoding in the browser, the question marks still appears.

Workaround: Edit the JSE file header to read <%@page contentType="text/html; charset=UTF-8"%>.

6329455 Cannot set context path for standalone web modules when WebSphere is set as the target server

Description: If you create a web module and set WebSphere as the target server, no matter which context path you set in the New Wizard, the target server reverts to an empty string in the project properties and the web module deploys with a context path that equals to /.

Workaround: Deploy the web module from IBM WebSphere's web administration console, specifying the desired context path:

1. Build the web module, do not try to deploy the web module.
2. Launch the IBM WebSphere's web administration console.
3. From the menu, Choose Applications > Install New application.
4. Specify the path to the web module's archive file and the desired context root.
5. Press Next and follow the instructions provided by WebSphere.

6330744 no AS and Pointbase node on Runtime if non-root user start IDE on UNIX.

Description: JSE8 was installed by root. When you use JSE8 as non-root user there are no predefined Pointbase connections under the Databases node of the Runtime window. Also, no Pointbase node is created under Databases > Drivers. Therefore, you cannot connect to Pointbase.

Workaround: Do the following:

1. In the Runtime window, right-click the Servers node and choose Add Server.
2. In the Server drop-down menu, select Sun Java System Application Server 8.1 and click Next button.
3. In the Add Server Instance window, specify Username and Password and click Next button.
4. Click Finish button.

6332414 Redeploy Web Application doesn't work

Description: After deploying and then modifying the web application, you cannot redeploy it using WebSphere as your server. The problem exists because the plugin deploys the web application as a new one. The deployment fails because the same context-root is already registered on the server.

Workaround: Before you redeploy, stop or undeploy the previously deployed web application manually using WebSphere Administration Console.

6332417 Redeploy EJB Module doesn't work

Description: After deploying and then modifying an EJB module, you cannot redeploy it using WebSphere as your server. The problem exists because the plugin deploys the EJB module as a new one. The deployment fails because the JNDI names are already registered on the server.

Workaround: Before you redeploy, stop or undeploy previously deployed EJB Module manually using WebSphere Administration Console.

6332419 Redeploy J2EE Application doesn't work

Description: After deploying and then modifying a J2EE application, you cannot redeploy it using WebSphere as your server. The problem exists because the plugin deploys the J2EE application as a new one. The deployment fails because the J2EE application is already registered on the server.

Workaround: Before you redeploy, stop or undeploy previously deployed J2EE application manually using WebSphere Administration Console.

6322428 I18N - cant simulate if provider xml has mbyte as part of its name - file not found when simulating

Description: You cannot simulate your application if the provider or portlet XML file has multibyte as part of the file name. You receive a file not found message when you attempt to simulate your provider application or portlet application. The Simulator will not work properly because the multibyte is not being interpreted correctly.

Workaround: Do not use multibyte in the name of a provider or a portlet.

6335478 CD&DVD: it takes too long to get installer window on solaris

Description: When you install JSE from CDROM/DVD media for Solaris (SPARC and x86), the installer window takes too long to launch. This problem occurs because the installer invocation time is longer.

Workaround: After clicking ok in the launcher, wait approximately 3 minutes for the installer window to launch.

6335731 RE does not place elements in packages (even if they are fully qualified in source code)

Description: When you reverse engineer Java source to a UML model, the model elements for any items from imported packages are placed in the root of the model rather than in the proper package.

Workaround: The IDE creates the correct package structure during the reverse engineering process. Drag and drop the incorrectly located model elements from the model root to the correct package.

6336206 CD&DVD: cannot start jse8 installer on solaris on some machine

Description: On some Solaris machines, the JSE installer does not start. The JSE installer fails with the following notification: could not utilize start class: com.installshield.wizard.Wizard. In some cases, if the /var/tmp partition is full on Solaris, the java command cannot execute the installer properly.

Workaround: Free some space in the /var/tmp directory.

F. How To Submit a Bug or Product Request

Submit a product defect (or request an enhancement) by using the Java Studio Enterprise IDE's Help Menu. In the IDE, select Help > How to Submit a Bug. To submit your product request, use the technical feedback page that appears.

G. Related Documentation

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