SDK Update 5 Release Notes

SDK Update 5 Release Notes

About the SDK Update 5 Distributions

The SDK Update 5 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 Platform, Enterprise Edition 5 SDK Update 5 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.

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):

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

To enable the Update Center to perform periodic checks and automated updates:

Start the Update Center.
On Unix: <installdir>/updatecenter/bin/updatetool
On Windows: <installdir>\updatecenter\bin\updatetool.bat

Select the Preferences tab.

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.

Specify the desired day of the week and time of the day for the update.

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

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.

The SDK includes a subset of the functionality available from Open ESB V2, 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.1 which is part of the SDK tools bundle.

Open ESB: The Blueprint samples used in the SDK do not run with JDK 5 for the Open ESB component.

The Java SOAP client class file needs to be compiled with JDK 6.

Workaround: JDK 6 is required to run the SOA BPEL blueprints.

6686497

Java EE 5 Samples: Unable to run Enterprise samples with NetBeans 6.x

Workaround: Because of a change in the default behavior of NetBeans IDE 6.x when a samples main project is opened, the corresponding sub-projects are not opened. These sub-projects are needed to successfully build and run the sample. To eliminate this problem, 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.

Sometimes, because of NetBeans caching, the sample may not work correctly. Follow these steps to correct this problem:

Close the NetBeans IDE and remove the .netbeans directory from your home directory to make sure nothing is cached.

You may want to rename the .netbeans directory, instead of deleting it.

Restart the NetBeans IDE and the Application Server.

Open the specific sample project and remember to check "Open Required Projects" otherwise you'll encounter "file not found exception."

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.