SDK Update 3 Release Notes

SDK Update 3 Release Notes

About the SDK Update 3 Distributions

The SDK Update 3 distributions provide a free integrated development kit to build, test, and deploy Java EE 5-based applications. The SDK also supports the newly released Java Platform, Standard Edition 6 and the latest technologies of the Java Platform, Enterprise Edition 5 (Java EE 5) Specification. Java Application Platform SDK Update 3 Beta focuses on streamlining enterprise application development and improving developer productivity. With the all-in-one bundle, developers can quickly learn, develop, and deploy new enterprise Java technologies. This is a free release and is based on the source code developed by Sun engineers and the open-source community.

The following distributions are available:

  • Java Platform, Enterprise Edition 5 SDK Update 3 bundle includes these components:
    • Sun Java System Application Server 9.1 FCS
    • Java Platform, Enterprise Edition 5 Samples
    • Your First Cup: An Introduction to the Java EE Platform
    • Java BluePrints
    • API documentation (Javadocs)


  • Java Application Platform SDK Update 3 Beta bundle includes these components:
    • All contents of Java Platform, Enterprise Edition 5 SDK Update 3
    • Portlet Container 2.0 Beta
    • Web Services for Remote Portlets 1.0 Beta
    • Open ESB V2 Preview 3
    • Sun Java System Access Manager 7.1 Patch 1 Early Access


  • Tools download additionally includes:
    • All contents of Java Application Platform SDK Update 3 Beta
    • Portal Pack 2.0 Beta
    • NetBeans IDE 6.0 Beta 1

Developers have the option to download the SDK bundles with JDK or Tools (NetBeans).

What's New

About Application Server 9.1 FCS

The Application Server release (Glassfish) builds on the quality and feature-rich Beta 2 to provide higher value add features for the enterprise. The Application Server 9.1 features inlcude clustering, in-memory replication, more improvements to the Grizzly-based HTTP engine, enhanced administrative functionality, improved self management capabilities, update center functionality that allows installation and/or updates of additional components, and much much more.

About Update Center Usage

When the Update Center is enabled, it performs an automated software update. During this automated update process, the Update Center collects and transmits the following data to Sun Microsystems (or its service provider):

  • Unique installation ID (GUID)
  • IP address
  • Operating system information (name, version, architecture, locale)
  • JDK version
  • Module download information (module name, date, time, status, download time, number of bytes downloaded)

No personally identifiable information is tracked. No personally identifiable information is associated with any other data or used for reporting purposes.

To ensure explicit agreement of the automated update, the Update Center is disabled by default. To enable the Update Center to perform periodic checks and automated updates:

  1. Start the Update Center.
    On Unix: <installdir>/updatecenter/bin/updatetool
    On Windows: <installdir>\updatecenter\bin\updatetool.bat
  2. Select the Preferences tab.
  3. In the Update Scheduling window, change the Check for Updates drop-down box value from Never (Manual) to a desired value. For example, daily or weekly.
  4. Specify the desired day of the week and time of the day for the update.
  5. Select the Save button to save your changes.

The Update Center will now automatically check for SDK component updates according to the schedule specified. When an update is available, the Update Center will launch and notify you of the component available to update.

About Web Services for Remote Portlets 1.0 Beta

Web Services for Remote Portlets (WSRP) delivers an implementation based on the specification defined by the OASIS Web Services for Remote Portlets. WSRP is a web services protocol for aggregating content and interactive web applications from remote sources. It is the means of aggregating (and publishing on the other end) remote "visual services", i.e. it does not aggregate data itself, but the "view" to the data. It is a "presentation oriented" web service, as opposed to the traditional "data oriented". Since it is based on presentation; WSRP enables seamless delivery and integration of entire web applications (or components thereof), their presentation layer inclusive. WSRP Primary features include:

  • Provides a WSRP Producer.
  • Provides a WSRP Consumer that can consume Remote Portlets exported by any WSRP Producer.
  • Includes a WSRP Test Driver built over the WSRP Consumer to provide a test enviornment.
  • Includes WSRP Mbeans with sample admin server through a WSRP administrative interface.
  • Includes WSRP Admin Portlets to provide an user interface for the WSRP administrative interface.

About Open ESB V2 Preview 3

The SDK includes a subset of the functionality available from Open ESB V2 Preview 3, including the JBI runtime, the Java EE Service Engine, and the HTTP Binding Component. This provides Java EE developers an introduction to composite application development that uses SOA technology. The tooling for this runtime is provided through NetBeans IDE 6.0 Beta 1 which is part of the SDK tools bundle.

About Sun Java System Access Manager 7.1 Patch 1 Early Access

Access Manager provides the first identity and access management solution to extend security for Web and Java applications to federated environments and Web services security -- with a single product.

About Java Platform, Standard Edition Development Kit 6 Update 3

The Java Platform Standard Edition Development Kit (JDK) includes the Java Runtime Environment (JRE) and command-line development tools that are useful for developing applets and applications.

Support for NetBeans IDE 6.0 Beta 1

Learn how easy it is to develop Java desktop applications with the improved GUI Builder in NetBeans IDE 6.0 Beta 1.

Removal of Sun Web Developer Pack from the SDK

As more developers move to the open source community, it is important to deliver bug fixes and enhancements in a more rapid manner. There is a new class of enterprises that care about scale and efficiency in ways historically unseen by the industry. These redshift companies are expanding rapidly; and see IT as providing a competitive advantage (see video).

To better serve our developers and to provide the best possible user experience and choice, the Sun Web Developer Pack (SWDP) components have been moved to the Update Center. This affects the SWDP component's which include: JMaki, Phobos, Dynamic Faces, Rome and WADL. By moving the SWDP to the Update Center, the development community will receive the latest and greatest SWDP functionality faster. The benefits of moving the SWDP component's are:

  • Smaller initial download size
  • Download only the components that you want
  • Obtain the latest releases you are interested in
  • Delivery of bug fixes and enhancements in a more timely manner


System Requirements

The following are the Supported Operating Systems in the SDK distributions:


Operating System Minimum Memory Recommended Memory Minimum Disk Space Recommended Disk Space JVM
Sun Solaris 9, 10 (SPARC)
Solaris 9, 10 (x86)
512 MB 512 MB 250 MB free 500 MB free Java SE 5 and 6
Red Hat Enterprise Linux 4.0 512 MB 1 GB 250 MB free 500 MB free Java SE 5 and 6
Macintosh (Intel, Power) 512 MB 512 MB 250 MB free 500 MB free Java SE 5
Windows Server 2003
Windows XP Pro SP1+
Windows Vista Business
1 GB 2 GB 500 MB free 1 GB free Java SE 5 and 6

Known Issues and Limitations

The following issues are related to the SDK bundles. Consult the following component release notes for issues related to these components:

ID Description / Workaround
none First Cup: In Chapter 4: Building and Packaging firstcup-dukes-age using ant, step 3 is an incomplete sentence.

Workaround: You can safely ignore step 3, so the instructions should read:

1. Verify that you have added the Ant build tool that comes with the Application Server to your path. The location is the lib/ant/bin directory of your Application Server installation.
2. In a terminal, go to <INSTALL>/firstcup/example/firstcup-dukes-age.
3. Enter the following command: ant
6599439 Correct the Access Manager Samples documentation.

The Access Manager samples document metions an incorrect username/password for logging into the AM Server console.
Document location C:\Sun\SDK\blueprints\ws-security\stock-jaxrpc\index.html The document advises to login using the amadmin user name and password. However, the Application Server user name and password should be used instead.

Workaround: The document should read as follows:
Login to the default administrator account using the appserver user name and password. After logging in to the console, follow this procedure."
6571551 Blueprints Samples: Actual vs. Expected Outputs when logically compared are correct, but when doing a text compare different.

Blueprint samples run successfully and produce output. However, using a text editor comparison tool, the expected output and the actual output has many differences.

Workaround: none; will be fixed in the next release.
6543014 Cannot display jmaki chart in Netscape 8.1.3, Mozilla 1.7 and Safari 2.0.4 browsers.

The following error is displayed:
Error loading jmaki.widgets.jmaki.charting.line.Widget: 
jmaki/charting/line/component.js (line:5437).
Message: area.initialize is not a function
Workaround: The charting display is fine using Internet Explorer 6 & 7, and Firefox 2.0.
6524792 Macintosh: Unable to install SDK on an iMac machine.

The following exception occurs when installing SDK on MacOS 10.4.8 operating system:
Exception with ../package/libPassword.jnilib file
Additionally, if installation is attempted with the --console option the installer hangs and displays the following error message:
   "CFMessagePortCreateLocal(): failed to name 
   Match port (java.ServiceProvider)
   See /usr/include/servers/bootstrap_defs.h for the error code.
Upon further examination, the /usr/include directory does not exist.

Workaround: Use the SDK installer in GUI mode to install.
6487340 Access Manager: Unable to set character encoding UTF-8 on Java Application Platform SDK 5 (without JDK) start up.

Workaround: A warning is issued according to the servlet specification. The javadocs of javax.servlet.ServletRequest.setCharacterEncoding() indicates:

Overrides the name of the character encoding used in the body of this request. This method must be called prior to reading request parameters or reading input using getReader(). Otherwise, it has no effect.

A webapp is calling this method after the request has moved to a state where this method is not supposed to have any effect. This will be fixed in the next release.
113389 NetBeans: Runtime exception on executing XSLT Bridge service test.
To resolve the issues related to the transform map file used by the XSLT Service Engine, installation of the latest version of the XSLT Service Engine (XsltSE) and the Transform Shared Library (TransformSL) is required.

Workaround: To install the XSLT Service Engine:

1. Download the XSLT Patch.
2. Unzip the files containing the installer jars for both XsltSE and TransformSL.
3. Extract the contents of the patch into a local folder.
4. Uninstall the existing XsltSE.
5. Uninstall the existing TransformSL.
6. Reinstall the TransformSL ( transformlib.jar file from the extracted patch).
7. Reinstall the XsltSE ( xsltserviceengine.jar file from the extracted patch).
8. Consult the Open ESB documentation for instructions on how to install a Shared Library and a Service Engine.
9. Start XsltSE.
112710 NetBeans: Sample EAR Projects build fails if required projects are not opened first time.
Because of a change in the default behavior of NetBeans IDE 6.0 Beta, when a samples main project is opened, the corresponding sub-projects are not opened. These sub-projects are needed for to successfully build and run the sample.

Workaround: select the sub-projects by checking the corresponding check box when the main samples project is opened. Then, follow the instructions as outlined in the sample documentation.
102389 NetBeans 6.0: Encountered 'Unable to convert normalized message to Prepared Statement' with Oracle.
The classes12 and ojdbc14 drivers does not support prepared statement metadata calls. Use data direct drivers for oracle.

Workaround: JDBC Binding Component only supports data direct drivers for Oracle database.

Left Curve
Java SDKs and Tools
Right Curve
Left Curve
Java Resources
Right Curve