Release Notes for Sun™ Java™ Studio Enterprise 7 2004Q4

For the latest information on this new release of the Java Studio Enterprise IDE, see the Source for Developers website at http://developers.sun.com/jsenterprise

This section of these Release Notes ...	Provides this information ...
A. Introduction	Introduction to these release notes and the Java Studio Enterprise product.
B. What's New: Enhancements and New Features	New features and enhancements for this release of the Java Studio Enterprise product.
C. Limitations	Limitations on usage of the Java Studio Enterprise IDE.
D. System Requirements	Hardware requirements needed to install a minimum Java Studio Enterprise configuration on any of the supported platforms.
E. Operating Systems, Servers, Databases, ORBs and Version Control Systems	Operating systems and other software supported by this release.
F. Platforms	Operating systems on which the Java Studio Enterprise IDE runs.
G. Installation Notes	Highlights of the new two-part flexible installation process.
H. Module Notes	Information about individual modules.
I. Bugs and Issues	Bugs and Issues related to functionality in this release of the product, with workarounds where applicable.
J. Accessibility	Accessible features of this product.
K. NetBeans Open Source Project	Sources of information about the NetBeans Open Source Project.
L. Redistributables	Redistributable binary files supplied with the IDE portion of the Java Studio Enterprise product.
M. Links to Selected Sun Java Studio Enterprise Product-Bundled Server Product Release Notes	Table of links to release notes for selected servers bundled with the Java Studio Enterprise product.

A. Introduction

Sun Java Studio Enterprise consolidates Sun's developer tools and server products into a single, enterprise-level integrated development environment (IDE). The IDE supports develop-to-deploy scenarios on servers that are also part of the Java System.

This latest release of the IDE offers tools and features designed to increase the productivity and efficiency of each software developer and the whole team:

• The new UML Modeling feature--visual and intuitive--quickly shows your code structure.

• The new Profiling feature lets you see at a glance what's going on in your application.

• The new Collaboration feature lets you work virtually with others to solve complex problems from within the IDE.

• The new Refactoring feature lets you rapidly reuse small chunks or great masses of code.

B. What's New: Enhancements and New Features

The following new features have been integrated into the IDE within the Sun Java Studio Enterprise product. (Also see Module Notes.)

• UML 2.0 modeling support. The UML Modeling feature is integrated into the IDE. This feature fully complies with existing UML standards and the soon-to-be-finalized UML 2.0 specification. Advantages of this feature:
  • Support for all diagrams, objects, attributes and defined relationships in UML

  • Live, markerless round-trip modeling and real-time source synchronization

  • A design center for pattern-based development--a pattern catalogue, and support for your custom patterns

  • Markerless reverse engineering to help you analyze existing code bases quickly

  • Generation of HTML documentation for your UML projects

• Enterprise application profiling. The IDE includes a Profiler that offers:
  • Comprehensive J2EE transaction monitoring. Capture all browser-based transaction details in the J2EE application, including the transaction round trip. Present the data in table and graphical chart form for detailed analysis.

  • Method-level profiling. Analyze your application's design and behavior with performance information--saved as a retrievable results tree--and selectively instrument methods in any application you deploy on the target application server.

  • Memory profiling. Probe the application server for memory data, and display it over time.

  • Load testing. Simulate load conditions--the number of users, the think time per user--and stress-test your application design early in its development cycle.

• Developer collaboration support. Sun Java Studio's Developer Collaboration feature gives you:
  • Code-aware instant messaging. Chat over the intranet or internet and across firewalls with multiple developers in your work group. This feature interprets Java, XML and HTML code with code-editing capabilities such as syntax coloring, code completion, and code documentation pop-ups.

  • Real-time file sharing. Organize code walkthroughs and collaborate with multiple members of a distributed team. Your team can simultaneously work on different parts of the same file. Temporary guard block depictions allow for intuitive collaboration on shared files.

• Refactoring support. The IDE includes a module with which you can rapidly refactor your applications. This Refactoring feature enables:
  • Moving and renaming classes, fields, and methods

  • Finding usage

  • Encapsulating a field

  • Extracting a method

• JavaHelp 2. The IDE uses the latest release of JavaHelp, which offers the IDE user improvements such as multi-topic printing.

• Fixes for earlier problems:
  • Installation. The JSE Portal can now be installed on a multi-partitioned PC using FAT32 on Windows. (This was Bug 5006945.)

  • Debugging EJBs. The IDE's debugging capabilities have been improved.

  • Performance. The new NetBeans windowing capabilities (described next) and performance improvements in the IDE remove various issues of the previous release.

• NetBeans 3.6 for most features. The new IDE is based on NetBeans 3.6 except for J2EE and Web development functionality, which are supported at the J2EE 1.3 level.

• New Look & Feel. The IDE's new, more seamless look & feel matches the underlying operating system: native L&F for Windows, and Java (Metal) L&F for all other platforms. (To set a different L&F, start the IDE with the --laf LaF_class-Name switch.) Also, the IDE's property sheets have been redesigned to provide a better view of all object attributes.

• New Windowing Capabilities. You can now simply drag and drop windows, and preview your new windows layout. Navigation is faster and easier: Ctrl-` toggles through your open IDE windows and documents. When you start a particular task, the windows related to that task are displayed automatically.

• New and Improved Editing Capabilities. The Source Editor supports code folding. Closing brackets, quotes, and parentheses are inserted automatically. To-do items you mark in the editor appear seamlessly in the To-Do window. Inherited methods are automatically called out in the margin. The Source Editor displays compilation errors in mouse-over tooltips, lets you view multiple documents at once, and integrates the Form Editor. You can output any Java file as HTML for web publishing. Clone View lets you view different parts of a document at the same time.

• Ant 1.6.1 Support. Managing the Ant classpath and versions of Ant is easier.

• JUnit 3.8.1 Support. You can automatically generate tests and test suites in both text and GUI mode.

• Version Control Integration. The IDE now supports PVCS and Microsoft Visual SourceSafe (VSS) for the Windows platform. In CVS, the client and the command-line interface now use the same GUI. The VCS command output display has been improved.

C. Limitations

• Using the Developer Collaboration feature with a firewall.
  If you don't want to turn off your system's firewall while using Collaboration and the IM server, then allow access to port 5222.

• UML Modeling limitations.
  • The UML Modeling Round Trip and Reverse Engineering features do not support classes that are defined inside methods.

  • EJB design patterns in this release of the UML Modeling feature do not support the deployment of EJB components within the IDE, or the IDE's EJB test client. (Bug 5077421)

  • Some required import statements are not inserted in the source code of generated classes. However, you can add them manually, choosing Add Imports from the contextual menu in the source editor.

  • To access a UML project checked into a source code repository, you must name your Java Studio Project the same name that was used when the UML project was initially created. In teamwork situations, all team members must use the same name for their Java Studio Projects.

• One IDE instance per user directory. In the NetBeans 3.6 release, it is no longer possible for more than one instance of the IDE to simultaneously use the same user directory.

D. System Requirements

The following table lists the system requirements for installing an IDE configuration on any of the supported platforms. The columns to the left represent the type of requirement: hardware system, memory, and disk space. The columns to the right show the requirements for each platform.

Note: The Solaris™ 10 platform, running Gnome on UltraSPARC® III and x86, is tested, but not supported, in this release of the IDE.

Note: Most of the space required for Optional Servers is used in the install path, but about 80 MB is used in /var/opt and /etc/opt.

E. Operating Systems, Servers, Databases, ORBs and Version Control Systems

The following table shows the products supported by the Sun Java Studio Enterprise IDE.

The SunRay server is supported as a multi-user platform.
The UML version supported is UML 2.0 Draft.

All bundled servers include local and remote configurations, except that Web Server does not support remote deployment.

F. Platforms

Software platforms:

J2EE:

• J2EE 1.3 (J2EE 1.2 or lower files are converted automatically to J2EE 1.3)

J2SE:

• JDK 1.4.2_05 (32-bit JVM only) - This is the certified platform.
• JDK 1.4.1_06 (32-bit JVM only)

Multi-User Hardware Platforms:

SunRay server

Note: The Java Studio Enterprise software contains all the components of the Java Enterprise System for development purposes only. Those licenses cannot be used for deployment.

G. Installation Notes

Sun Java Studio provides an entire set of tools and servers on one DVD, on two CDs, or in two download files. You can quickly install the tools that you need to get started, and then install optional servers at your convenience--now or later. You can tailor your download and your installation to your needs.

For example, if you already have supported servers installed, you might want to install only the IDE. Or, you can install only the server you need. The installer enforces all the necessary dependencies.

The DVD includes files that contain the IDE and all bundled components for all supported platforms. The two CDs or files, each set provided for a platform, contain the following components and servers.

CD 1 or File 1 Tools Components	The Java Studio Enterprise IDE Application Server Message Queue Collaboration Runtime
CD 2 or File 2 Optional Servers	Web Server Directory Server Access Manager Portal Server

When you insert the DVD, the installer is not invoked automatically. Instead, a web page appears asking you to make choices.

See the Sun Java Studio Installation Guide for complete information on installing the product.

H. Module Notes

UML Modeling

• If you have used the UML Modeling feature to model a class, and later you use the editor to define a field manually, the IDE automatically adds a getter method and a setter method. This also happens if you create a class, then use UML Modeling on the code (for example, Reverse Engineering or Tools > Update Model From Source), and then open the source in the Source Editor. The IDE automatically creates getter and setter methods for any field that does not already have getter and setter methods.

  To prevent the IDE from adding these methods, do the following:

  Main Menu > Modeling > Preferences > Round Trip Engineering > Java > Create Accessor Methods

  Set this property to No.

• If you go to the project tree to change the name of a comment element, the new name of the comment also replaces the body text of the comment. (Bug 5070917)
  Workaround: Use the UML property editor to rename the comment.

Refactoring

• Compilation errors can occur after some refactoring actions.
  When you perform refactoring on your code using the Refactoring submenu actions, the IDE warns about most, but not all, compilation errors that will occur if you continue with the refactoring action. The following list shows some of the potential compilation errors that the IDE does not catch.
  Warnings not displayed by the IDE:
  • Moving classes with protected members to another package (Bug 5081618).

  • Renaming a method that is overridden by classes that extend the class (Bugs 5074837 and 5069665).

  • Moving overridden methods, overriding methods, overridden fields, or overriding fields (Bugs 5075343, 5082178, and 5082230).

  Workaround: After each refactoring action, choose Build All from the Build menu to ensure that no code has been broken. If you do this after each refactoring action, it's easier to diagnose errors. Running JUnit tests after each refactoring is also good practice.

• Be aware of interoperation between Refactoring and UML Modeling.
  If your project is associated with UML Modeling and you want to use the Refactoring actions, it's best to create a new project and use it for Refactoring purposes. If you have reverse-engineered or synchronized the code, then your project is associated with UML Modeling.
  The following issue can arise when you use Refactoring actions in source code for which UML Modeling is monitoring and applying automated actions.

  If you use the Refactor > Rename action on a field that has getter and setter methods, UML Modeling sees the name change and automatically changes the getter and setter method names. Therefore, even though the Refactoring Preview window does not show the getter and setter methods, they are changed as well.

  While the Refactoring action changes the field name in all mounted source code, UML Modeling changes only the getter and setter names in the current source file, thus affecting any other classes that use those methods. To avoid problems, manually change the method names back to their original names.

Web Application Framework

You might find that Execute Page > Execute Page(Redeploy) is not enabled on the contextual menu. If this happens, right-click Basic ViewBean(Page) to execute the page. If this choice is not enabled, then right-click the application and select Identify Module.

I. Bugs and Issues

Installation
Profiling
UML Modeling
Collaboration
Refactoring
Portlet Builder
JavaServer Pages
Web Application Framework
Servers
J2EE Debugger
Version Control
Miscellaneous

Installation

4973270 You can't install or uninstall in silent mode with a state file that was generated on a different host or platform.

Description: A state file might not work if it was generated on a different host machine, or on a different operating system. For example, if you're working on a Windows machine and you try to install in silent mode using a state file generated on a Solaris SPARC machine, the console might display a Corrupt statefile message. (All platforms)

Workaround: Edit the state file and then re-invoke the silent installer. Refer to the Sun Java Studio Installation Guide, Chapter 7, for specific instructions.

4981429 The Access Manager console (http://localhost/amconsole or http://machine-name.ntdomain/amconsole) redirects the user to the Portal.

Description: When Access Manager is installed on Web Server with a domain name (DNS suffix) of NTDOMAIN, the Access Manager console doesn't work. (All platforms)

Workaround: (Installing on Web Server) Be sure that your machine's domain name is in all lowercase characters, for example, ntdomain or sfbay.sun.com.

(Installing on Application Server) After installing the Access Manager on Application Server, edit the IS6.1/config/xml/amPlatform.xml file and remove the .ntdomain value from the iplanet-am-platform-cookie-domains setting. Be sure to do this just after installation, before you start the servers.

4981447 The Application Server might fail to start because of a port conflict.

Description: You uninstall an earlier version of the product and install the new version. You use the Start All Servers command. The Application Server administration console and instance might fail to start. (Windows)

Workaround: Edit the server.xml file (located in the config folder) as follows: Change ORBPORT to the number of an unused port.

4989825 The IDE directory is not installed on the network drive you specified, but on /opt.

Description: During installation, a network-mounted location was specified, but the SUNWjstudio directory was created on /opt instead. The install log showed the specified installing directory, but the IDE directory was not installed there. The IDE cannot be installed on an NFS-mounted file system. (Solaris)

Workaround: Install the IDE on a locally mounted disk partition.

5019983 The Application Server admin password is insecurely stored in /opt/SUNWappserver/statefile.

Description: After installation, the administrative password for Application Server is stored in a state file on the disk in plain text, with general read permission for root users. (Also see related Bug 6202864.) (Solaris)

Workaround: If the security of the admin password among your community of root users is an issue, you can manually change permissions on the state file to the level -r-------, using 400 with the chmod command. However, this might cause the plugin to forget your access data (Bug 6185561).

5081060 You have problems installing the IDE or some of the servers. The installer does not accept the DNS domain name.

Description: If your stand-alone Solaris system uses the Dynamic Host Configuration Protocol (DHCP) to configure your environment instead of static IP addresses, you might experience problems trying to install the IDE. (Solaris)

Workaround: Ping your local machine with the following command:

#ping -s fully_qualified_host_name

If this command fails, manually add the fully qualified host name (FQHN) to the /etc/hosts list as follows:

127.0.0.1 localhost loghost
IP_address host_name FQHN # added by DHCP

5101681 Canceled Web Server installation leaves stale registry keys.

Description: If you begin installing Disk 2, but then you cancel Web Server installation, the uninstallation process starts. However, entries have already been made in the registry, and some of these remain. (Windows)

Workaround: Manually clean out the system registry, removing any keys that contain the Webserver string. For details, refer to the Sun Java Studio Installation Guide, Chapter 15, in the section "Identifying and Fixing an Incomplete Uninstallation."

6201183 The Access Manager Server login page doesn't appear when Web Server, as the default container, uses a non-standard port.

Description: When your application uses Web Server as the default container and Web Server isn't configured to use the standard port (80), the Policy Agent isn't automatically configured to the right port. (All platforms)

Workaround: In the file studio_home\PolicyAgent\IdentityServer\j2ee_agents\config\e__Sun_ jstudio_04Q4\AppServer7\domains\domain1\server1\config\amagent.properties , change the Web Server port number to the actual port instead of default port, in the following keys:

com.sun.am.policy.amFilter.loginURL
com.sun.am.policy.amFilter.port.check.map
com.iplanet.am.server.port
com.iplanet.am.console.port
com.iplanet.am.profile.port
com.iplanet.am.naming.url
com.iplanet.am.notification.url
com.iplanet.services.cdsso.CDCURL
com.iplanet.services.cdc.authLoginUrl
com.sun.identity.agents.notification.url

Then restart the container server.

6202186 Application Server configuration fails on Solaris Sparc 8.

Description: Disk-1 installation fails if you choose to create a non-root instance of Application Server. (Solaris)

Workaround: Refer to the Sun Java Studio Installation Guide for detailed clean-up instructions.

6202864 The Application Server admin password is insecurely stored in /opt/SUNWam/SUNWam/j2ee_agents/.installer_inputs.

Description: After installation, the administrative password for Application Server is stored in an installer-inputs file on the disk in plain text, with general read permission for root users. (Also see related Bug 5019983.) (Solaris)

Workaround: If the security of the admin password among your community of root users is an issue, you can manually change permissions on the state file -r-------, using 400 with the chmod command.

Profiling

6195552 You might get a "Connection refused" or "Connection lost" message when you try to debug an application with Profiler enabled. Enabled

Description: (Windows XP) If you enable Profiler for a server instance, restart the instance, enable Profiler for an application, and attempt to debug the application, the debugging session might stop, and you might see the message "The connection was refused when attempting to contact [host name]."
(Solaris 8 on SPARC-S2) If you do the same thing, the debugging session might stop, and you might see the message "Lost connection to server instance" and eventually a message indicating that the session is stopped.

Workaround: Disable Profiler for the server instance. Disable Profiler Filter for the application. Then, stop and restart the server instance before debugging.

UML Modeling

5095083 The Web Report progress dialog box seems to hang the first time.

Description: When you choose Modeling > Report > Web Report, set your reporting options, and click Finish, the resulting progress dialog box seems to indicate that the system is not responding. (All platforms)

Workaround: Click Cancel in the progress dialog box. The web report isn't actually canceled; it is generated successfully.

This anomaly occurs only the first time you use the web report feature with a new user directory. After that, the progress dialog box responds as designed. In all cases, the report is generated correctly.

5110005 The justification options in the Doc pane stop working after you deselect or reselect the element.

Description: (Windows)

Workaround: Do any of the following:

• Edit the source HTML file of the class element to specify the justification you want. For instance:

  <p align="center">line 2</p>

  becomes

  <p align="right">line 2</p>

• Save the changes (Ctrl-S) in the editor.

• Delete and recreate the line where justification is not working.

6174892 In the UML Mount Wizard, the primary filesystem you specify by typing in the File Name field is ignored.

Description: This problem arises when you use the wizard to create a new project. (Click the Modeling tab. Type a path to the directory you want as your primary UML Modeling filesystem. Click Finish.) The file chooser's preselected directory is the one actually mounted, not the directory you specified. (All platforms)

Workaround: Instead of using the File Name field, navigate to the directory you want and select it.

6182658 When you're using the ClearCase version control system, you might get error messages.

Description: Although you suspect nothing is wrong, you might see redundant messages such as cleartool: Error: Element name is already checked out to view viewname or cleartool: Error: Can't create directory element because name already exists. (Windows)

Workaround: Ignore these messages and simply check to see that your additions to ClearCase have been made.

6183736 The Design Center might not display an element in a project that was named the same as a deleted project.

Description: You create a new design pattern project in the Design Center Catalog, name it, and remove it. You create another new project, but use the same name as the first. You then create a diagram in this new project. The diagram might not show up in the project tree; the project might appear empty. (All platforms)

Workaround: Restart the IDE. All new elements you have created in the new project now appear.

6185174 A text property can't be deleted using the property sheet.

Description: If you try to clear text from a property using the Property Editor, the text reappears. (All platforms)

Workaround: Use the source editor or the UML Documentation window.

6187139 Some menu items are absent when the overview window is open.

Description: If the overview window is open, the Insert/Delete Attribute and Insert/Delete Operation items don't show up in the context menu. (All platforms)

Workaround: Do either of the following:

• Close the overview window before opening the context menu.
• Use the property sheet for insertions or deletions.

6188808 Editing source code to change the multiplicity of parameters does not propagate the change to the model.

Description: When you create a class diagram, add a class, add a method, and then edit the method to change the multiplicity of its arguments or parameters, the UML model is not updated correctly. (All platforms)

Workaround: Right-click in the source editor and choose Tools > Update Model From Source.

- UML Modeling and Multibyte Issues

5100837 Adding an extends clause with multibyte characters can make the class definition invalid.

Description: You create a new project or class diagram, drop and name a class with multibyte characters, create an operation on the class, drop and name a second class, and use the source editor to add an extends clause so that the second class extends the first. You redefine superclass method. The code and model seem to be updated correctly. However, when you click in the project tree or the class diagram, the class definition syntax is not complete. (All platforms)

Workaround: Instead, in the source editor, paste the class name into the extends clause.

5103318 You can't enter multibyte characters for attribute or operation names in edit control or the project tree.

Description: Using edit control or the project tree to enter multibyte characters for attribute or operation names doesn't propagate the changes to the model. (All platforms)

Workaround: Use the property editor or the source editor instead.

5103320 You can't use edit control to enter more than one multibyte character when naming a class.

Description: Edit control does not propagate this input to the project tree. (All platforms)

Workaround: Use the project tree or the property editor instead.

6194570 A web report in a Japanese locale might show strings incorrectly.

Description: When a web report is generated, the encoding specification is always Shift-JIS for every HTML. But the encoding of the embedded strings, such as Diagram names, depends on the system locale. As a result, when the IDE is used in the EUC_JP environment, the actual encoding (EUC_JP) does not match the HTML encoding specification, and strings can appear garbled. (All platforms)

Workaround: If multibyte characters do not appear correctly in the web report pages, change the browser's encoding value to another encoding.

- UML Modeling and Version Control Issues

5110009 The IDE's main Versioning menu does not correspond to the Source Control menu in the UML Workspace pane.

Description: The main Versioning menu is intended to control file objects under the Filesystems tab, and does not match the functionality provided by the UML Source Control menu. UML Modeling elements can comprise multiple files. Inconsistent results can occur if you try to manually version the individual UML-related files. (All platforms)

Workaround: Use only the UML Source Control menu to apply versioning actions to UML Modeling elements.

6186711 When you commit a file, you might see two commit dialog boxes instead of one.

Description: You create a diagram and add an element to it. A dialog box asks if you wish to add the change to the repository, presenting the checkbox for the option Commit if successful. If you select this checkbox, you next see two dialog boxes, both asking for your approval.

Workaround: Don't check the dialog box for Proceed to commit. The system automatically does a commit.

6199175 On the first attempt, you might not be able to add a package to source control.

Description: You mount a new version-controlled file system and create a new UML Modeling project from it. You then create a new diagram and a package. You can add the project and the diagram to source control, but you might not be able to add the package. (All platforms)

Workaround: Try the action again from the contextual menu command.

6197911 When you're using version control and you add a class to a Class Diagram, you might get a Null Pointer Exception.

Description: When you add the diagram to the repository and check it out again in order to add elements, an NPE might appear. (All platforms)

Workaround: If the class is actually added, you can ignore the NPE.

6199207 The IDE doesn't show that the UML Modeling project is under ClearCase control, and
6199388 The IDE can lose the VCS status icon of the UML Modeling object after some VCS actions.

Description: Race conditions can occur between the UML Modeling version control interface and the user's mounted version control system. As a result, UML Modeling might report missing or incorrect versioning status on one or more model elements. (All platforms)

Workarounds: Try one of the following approaches:

• Expand the UML Modeling project node in the UML Workspace pane, and invoke Source Control > Refresh Status.

• If other users are checking work into the same source control repository, invoke Source Control > Get Latest Version. This can also be used in place of Refresh Status (as described in the previous item).

• In some cases, you might need to add the project to source control again, to restore the correct version control status.

See the Module Notes for more information on UML Modeling.

Collaboration

5071137 Session nodes are missing from the Collaboration window after login.

Description: After you log in, the node for the new session does not show in the session explorer view. Instead, the view simply shows "No active sessions". (Solaris)

Workaround: Close and reopen the Collaboration window.

5074617 File ownership might be transferred unexpectedly.

Description: If a user leaves a conversation, the ownership of that user's files might be transferred to another participant in the conversation. This can come as a surprise if the user had to leave the conversation because of a network problem. (Solaris)

5081098 Sharing and saving a visual form reopens the form window.

Description: This happens when a visual form file is being shared between IDEs. When the user of one IDE saves changes in the file, the form's Java and editor documents reopen to refresh the file. (All platforms)

Workaround: If you save a file in one IDE, close and reopen the file in the other IDE.

5087286 Pressing the F6 key might not always execute a Java class in the Shared Files area.

Description: If a user creates a Java class in the Shared Files area and then tries to use the F6 key to execute the class, it might not work. (Windows)

Workaround: Execute the Java class by right-clicking its node and selecting Execute from the contextual menu.

5092524 A shared file might not be renamed correctly.

Description: One user creates a class in the Conversation Shared Files area, and then renames the class. The other user still sees the original name on the class. The first user might receive a message saying the class can't be renamed. (Windows)

Workaround: To rename a shared file, do as follows:

1. Copy the shared file into a local filesystem.

2. Rename this file in the local filesystem.

3. Delete the shared file in the shared folder.

4. Copy the renamed file from the local filesystem to the shared folder.

5107314 You can't log in with a multibyte user name or password.

Description: You can't use multibyte or extended ASCII characters as a user name, a password, a public conversation name, or a display name in collaboration accounts or sessions. (All platforms)

6181648 The IM server might drop a filesharing connection if the file is too large.

Description: When a user tries to share a file bigger than the IM server's buffer limit, the connection can be dropped with messages including: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (Solaris)

Workaround: A file to be shared must not exceed the IM server's buffer limit. Users should be able to share a file as big as 1 MB.

6182376 A package can't be deleted after being built during filesharing.

Description: During a filesharing conversation, one user creates and populates a package in the shared files area, and the other user builds the package. If the first user quickly tries to delete the package, a message might appear saying that the package can't be deleted. The Collaboration filesystem might not have released the lock yet. (Windows)

Workaround: Wait a few moments and try deleting again.

6186295 The empty line added to a shared text, Java, or XML file is not for editing.

Description: During a filesharing conversation, one user shares a text, Java, or XML file, and the other user opens the file. The first user edits the last line in the file. In the second user's copy, an empty line is added to the end of the file. If the second user edits this line, the changes are not propagated to the first user's copy. (Windows)

Workaround: Don't edit the added empty line.

Refactoring

5055514, 5060310, 5075305, 5081618, 6184456 Caveats while using Refactoring to move classes and static members.

Description: Before using the Refactoring feature to move static members (methods or variables) across packages, make sure they do not reference, and are not referenced by, other protected members. For example, if you move a static protected method from one package to another, then it might not be visible after the move to classes outside the destination package. You can use Find Usage to perform such a check. You can also make these members public so that they are visible after the move operation.

While you are moving classes, if a file has more than one top-level class and if you move one of these classes, then the other top-level classes are moved automatically. When you move a class to a different package, sometimes you might find unnecessary or erroneous import statements, which you must remove or correct. (All platforms)

5058187 Refactoring sometimes does not recognize variables.

Description: Refactoring actions do not always recognize one-character variables, such as x[] or x++. (All platforms)

Workaround: Try putting a space after the variable.

5074078 Refactor > Rename Class changes all comments that use the object's old name.

Description: When you use the Refactoring feature to rename an object, be careful to review the comments section in the preview window. The IDE changes all comments that use the old name, regardless of whether they apply to the object being renamed. (All platforms)

Workaround: Clear the check box of any comment that you do not want the IDE to act on.

5070205 Issue with Undo/Redo in the core

Description: The Edit > Undo action does not undo the Refactoring > Rename action if the action was invoked from the contextual menu for a node in the Filesystems window. (All platforms)

Workaround: To undo a refactoring action that was generated from the contextual menu in the Filesystems window, first open the source file in the source editor.

6200832 Trying to refactor a view bean can produce a null pointer exception.

Description: You use Web Application Framework to create an application and, in it, a view bean. When you try to use refactoring operations in the view bean, such as renaming a variable, you get a null pointer exception. (All platforms)

Workaround: Before you do any refactoring, download and mount the servlet API JAR, which is available at http://java.sun.com/products/servlet/reference/api/index.html.

See the Module Notes for more information on Refactoring.

Portlet Builder

5097924 Simulator messages display as ?? for multibyte characters.

Description: When you're using Application Server, messages in the simulator do not come from localized bundle files. (This is not an issue when you're using Tomcat.) (All platforms)

Workaround: Do one of the following:

• Log into the simulator window 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 next (for Bug 5108171).

5108171 When using the packager in another locale, you might see messages displayed as ?? for multibyte characters.

Description: To use the packager in another locale and see localized messages displayed properly, you must manually set the Application Server instance locale. (This is not an issue when you're using Tomcat.) (All platforms)

Workaround: From the Application Server administration GUI, change the server instance locale (Locale entry on Advanced Tab for the server instance) to an appropriate locale. Or, leave the locale blank so that the server instance picks up the system locale when it starts up. Edit the locale field and save, and then apply changes and restart the server.

5104746 A property with multibyte characters that you set in the simulator doesn't display correctly.

Description: When you simulate a portlet application in an Asian locale, then you add a property string and choose Execute, the multibyte characters display improperly in the property sheet. (platform)

Workaround: Don't use multibyte characters in a property name or value.

6182165 A non-root user simulation fails on Tomcat if a root simulation hasn't already been done.

Description: A simulation attempt by a non-root user on Tomcat fails before the first simulation by a root user. No portlet*.jar files are copied into jwsdp/common/lib, which is write-protected. (Solaris)

Workaround: Do either of the following:

• Copy the jar files under user_dir/pb/data/commonlibs/ to install_dir/Ent_04Q4/jwsdp/common/lib

• Start the IDE as root, and then start as non-root.

6182257 A root simulation fails on Application Server if it has been installed with non-root user capability.

Description: In this case, Application Server has been installed so that non-root users have access. Now, a root user runs the IDE and tries a simulation. The IDE's user directory belongs to the root user, but the Application Server process is running under the non-root user's account (even if it was started by the root user from the root's IDE process). Thus, the server process tries and fails to write to /tmp/u1/system/SIMportletcontainer.log. (Solaris)

Workaround: Give write permission to any non-root user who should own Application Server for the following (create the log files if they don't already exist):

root_user_dir/system/portletbuilderapp.log
root_user_dir/system/SIMportletcontainer.log
root_user_dir/ps/web/tmp/portletDepolyer.log
root_user_dir/ps/web/WEB-INF/classes/

6194516 Portlet Set value disappears when the properties window is closed.

Description: You create a Portlet application and then a Portlet. In the Filesystems window, you right-click the Portlet application node and select Properties from the contextual menu. (In this case, don't open Properties from the Windows menu.) Open the Portlet Set and see the value in the property sheet. If you close the window and click the Properties window, the Portal Set value disappears. (All platforms)

Workaround: Click anywhere in the property editor, and the Portlet Set value reappears.

JavaServer Pages

4959762 JSP compilation fails if a bean class is not precompiled.

Description: If your JSP uses a bean through the jsp:useBean tag, and the bean class has not been compiled, then the JSP fails to compile. You might get an error message like this:
JSP.jsp [-1:-1] beans.Bean
Errors compiling JSP. (Windows)

Workaround: Compile all the bean classes in the JSP before compiling the JSP.

Web Application Framework

4960761 An application's display name might not appear correctly after conversion.

Description: When you use the Convert Application wizard on an application, the wizard might not load the application display name correctly from the web.xml file, and the name might not appear in the Application Properties window. (Windows)

Workaround: Open the Settings and Configuration node for the application, select the Deployment Descriptor, and edit the Display Name property.

5079813 An application might not run because the plugin doesn't recognize a module package.

Description: The Web Application Framework plugin does not always recognize a module package inside a Web Application Framework application. In most cases, this happens during the creation of the new application or after the IDE is started. (All platforms)

Workaround: Right-click the Application node and choose Identify Modules.

6201472 If you disable the Access Manager Security property in a web application and then try to run the application, you might get an error message (HTTP Status 500 Error).

Description: After you enable the web application's Security property, run the application, and then use the Other Configuration > Sun Java System Identity Server property editor (which is for Access Manager) to disable the Security property, the application's web.xml file still contains some security values. The web application won't open unless security is either re-enabled or fully disabled. (All platforms)

Workaround: Use the Other Configuration > Sun Java System Identity Server property editor to remove any remaining Security Constraints and Security Roles. Then, redeploy the web application.

Servers

4892779 CMP Module Initial selection produces an exception.

Description: You start the IDE normally. The first time you load and select a very large EJB module (with, say, 100 CMP beans and many CMRs), the IDE can seem to be proceeding normally, but then can give an unexpected exception. (Windows 2000)

Workaround: When you start the IDE, increase the available memory according to your system's capacity, using this option: -J-Xmxnnnm
where nnn is higher than the default start value of 256.

4965961 JWSDP1.3 feature enhancements can be used only on Application Server.

Description: The JWSDP1.3 software would need a jwsdp-common-lib.jar file for use in other supported application servers. (All platforms)

5015087 CMP mapping errors occur, and response time slows greatly, when a database schema or an EJB module (or, simply a very large EJB module) that was created in a much earlier version of the IDE is used in the current version.

Description: If you try to deploy in the current version of the IDE an EJB module or DBschema that was created in Sun ONE Studio 4, container-managed relationship (CMR) verification errors can arise. Relationships can be lost, particularly if the CMP bean has more than two relationships. Also, if you try to open a very large EJB module that was created in Sun ONE Studio 4, the IDE appears to hang. (All platforms)

Workaround: These errors are shown clearly in the output window. Correct them using the CMP beans' property sheets.

6176639 The example application appserver executes on the Access Manager with an exception, but is deployed successfully.

Description: The Policy Agent is not configured properly if the /usr/j2se directory does not contain JDK 1.4 or a more recent version. (Solaris)

Workaround: If you install either the Application Server or the Access Manager from JSE 7, be sure that the /usr/j2se directory, or a symbolic link, contains the required version of the JDK. If it does not, then create a symbolic link from the incorrect file path to the IDE install directory that contains the required JDK version.

Use this command to create the symbolic link: ln -s /usr/jdk/entsys-j2se /usr/j2se

6199998 When you try to run an application that has been configured to use the DataDirect driver, you might get a ClassNotFound exception.

Description: After you register a database connection pool, the server.xml file for Application Server is missing a slash, which makes it appear that DataDirect drivers don't work on Solaris. (Solaris)

Workaround: After creating and registering a connection pool, add the missing slash manually, as follows.

1. In the directory where the IDE is installed, open this file: /Appserver7/domains/domain1/server1/config/server.xml
   (Change this path according to the server instance.)

2. In this file, search for the classpath-suffix element.

3. Find the path to the jars named sm*.jar (for example, smbase.jar, smresource.jar).

4. Add a forward slash ( / ) to the beginning of the path.

6201117 Renaming DatasetNavigator or DatasetLocator components might lead to application errors.

Description: You add a view bean to an application created with Web Application Framework, add a DatasetNavigator (or DatasetLocator) component to the page, and rename the navigator or locator. When you open the view bean's JSP in the source editor, the <jato:datasetNavigator> tag is correctly updated, but the inner <jato:containerView> might not be. This situation would lead to application errors such as Invalid child name at runtime. (All platforms)

Workaround: When you rename one of these components, be sure to manually rename the nested containerView tags of the component.

J2EE Debugger

5065466 The IDE might appear to let you keep one debugger session going while creating a new session.

Description: You mount a J2EE application and start a debugging session on an EJB module in the application. The EJB module is deployed. If you try to start another debugging session on the same EJB module, a dialog box appears asking if you want to keep the existing session and start a new one. However, the second session doesn't start. (Windows)

Workaround: When you're debugging a J2EE application or an EJB module, if the debugger is stopped in a Java class such as the SessionBean class and you wish to restart the debugger, be sure you select the application or the EJB module node before restarting.

Version Control

5082087 Under VSS, revisions of a text file are opened in NotePad, and an exception is thrown.

Description: You create a text file (.txt), put it under VSS control, and create several revisions of the file. You invoke Show Versions on the file and expand file revisions. You right-click any of the revisions and select Open. Instead of the output scrolling at the command line, it appears in a .txt file. When you close the .txt file, the IDE throws an exception. (Windows)

Workaround: This happens when notepad.exe is designated as the application with which you will view .txt files. To cure the problem, explicitly remove any association between an application and .txt files: In the database ss.ini file, add the following Extension_Association line:
.txt =
This line ensures that files with the extension .txt are not associated with an application.

5104939 Sometimes, when you right-click a web.xml node that is under version control, the IDE keeps asking you if you want to get a writable file from the version control system.

Description: You mount any VCS file system, create a new web module in it, add the web module to the repository, and right-click the web[Current] node to view properties. Or, you run another command from the contextual menu. However, the IDE keeps asking if you want to check out a file. (All platforms)

Workaround: Before you add a web module to your version control system, make sure you open the Properties window for the web.xml node. This forces the initialization of the server-specific files for the web module.

Some version-control bugs arise only when you're using the UML Modeling feature. See that section for details.

Miscellaneous

5091569 An external browser window does not open from the IDE as expected.

Description: If you use Mozilla as your web browser, and you have the IDE open but you don't already have an instance of Mozilla running, the browser window might not open when you try to invoke it from within the IDE. (All platforms)

Workaround: Open a browser window outside the IDE. The IDE will reuse the window.

J. Accessibility

Documentation

Sun Java Studio Enterprise developer tool and server documentation is provided in accessible formats that are readable by assistive technologies.

Online Help Documentation in the IDE

The IDE provides many accessibility features that enable you to read about and use the product in the manner that is most comfortable and convenient to you. These features include:

• Mnemonics and keyboard shortcuts
• Customizable fonts
• Customizable colors
• Customizable toolbars
• Customizable stylesheets

For information on the accessibility features of the IDE, open the the online help and click the Accessibility topic in the table of contents.

Modifying Cascading Style Sheets for Accessibility

The instructions in the online help for modifying the cascading style sheet require additional information.

Most help sets use the style sheet that is stored in modules/docs/usersguide.jar. If you change this style sheet, the display of most other help sets is also affected. The exception includes the Database Schema help set, which uses the style sheet stored in dbschema.jar.

To change the cascading style sheet for the online help:

1. In your IDE installation directory, navigate to modules/docs.

2. Use the jar command-line utility to unpack the JAR file.

On Microsoft Windows and UNIX systems, the command is:

jar xf jar-file

For jar-file, use one of the following:

• usersguide.jar - Style sheet for most help sets
• dbschema.jar - Database Schema online help

The Jar tool makes copies of the files and writes them to the current directory. The directory structure is reproduced according to the package structure in the archive.

3. In the extracted hierarchy, navigate to the directory that contains the style sheet you want to edit:

• General online help - org/netbeans/modules/usersguide
• Database Schema - com/sun/forte4j/modules/dbmodel/docs

4. Open the file ide.css in a text editor. Edit the file to your preferences and save the file.

6. Return to modules/doc in your installation directory and update the JAR file. On Microsoft Windows and UNIX systems, the command is:

jar ufv jar-file input-file

For jar-file use the name of the original JAR file, for example, usersguide.jar. For input-file use, one of the following:

• org for the Users Guide help set
• com for the Database Schema help set
  

Solaris Operating Environment

The Solaris operating environment allows you to set window behavior using the Window Style Manager. When using mnemonics with the Sun Java Studio Enterprise IDE, the window behavior should be set to "Click In Window To Make Active."

If this option is not set, in some cases, a mnemonic can appear to fail.

K. NetBeans Open Source Project

The IDE is based upon the NetBeans Open Source Project, located at http://www.netbeans.org. NetBeans is a community-based project that fosters the use of the NetBeans IDE platform in new, creative ways. All developers are invited to join the effort to extend the NetBeans IDE and improve the framework upon which it is based in order to create an extremely powerful set of tools by and for the development community.

L. Redistributables

The following binary files are supplied with the Sun Java Studio Enterprise IDE and are redistributable:

• dbschema.jar
• xerces-2.6.0.jar
• cvslib.jar
• AbsoluteLayout.jar
• sql.jar
• standard.jar
• jaxen-full.jar
• jstl.jar
• saxpath.jar
• jato-2_1_4.jar

M. Links to Selected Sun Java Studio Enterprise Product-Bundled Server Product Release Notes