Sun Java Solaris Communities My SDN Account Join SDN
 
SDK Update 3 Preview 2 Release Notes
Free yourself from complex code.
Reduce development time. Add convenience.  
Begin Product Tab Sub Links At a Glance Features Active Sub LinkDocs & Resources

SDK Update 3 Preview 2 Release Notes


About the SDK Update 3 Preview 2 Distributions

The SDK Update 3 Preview 2 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 Preview 2 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 Preview 2 bundle includes these components:

    • Sun Java System Application Server 9.1 Beta 2
    • Java Platform, Standard Edition Development Kit 6 Update 1
    • Java Platform, Enterprise Edition 5 Samples
    • Your First Cup: An Introduction to the Java EE Platform
    • Java BluePrints
    • API documentation (Javadocs)

      Tools download additionally includes:
    • Sun Web Developer Pack Release 1
    • Open ESB 2.0 Beta 2
    • Sun Java System Access Manager 7.1 Patch 1 Early Access
    • Portlet Container 1.0
    • NetBeans IDE 6.0 Preview with SOA (formerly NetBeans Enterprise Pack)

  • Java Application Platform SDK Update 3 Preview 2 bundle includes these components:

    • All contents of Java EE 5 SDK Update 3 Preview 2
    • Sun Web Developer Pack Release 1
    • Open ESB 2.0 Beta 2
    • Sun Java System Access Manager 7.1 Early Access
    • Portlet Container 1.0
    • NetBeans IDE 6.0 Preview with SOA (formerly NetBeans Enterprise Pack) (tools download only)

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

What's New


Application Server 9.1 Beta 2 (Glassfish)

The Application Server Beta 2 release (Glassfish) builds on the quality and feature-rich Beta 1 to provide higher value add features for the enterprise. The Application Server 9.1 Beta 2 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.

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.

Open ESB 2.0 Beta 2

The SDK includes a subset of the functionality available from Open ESB 2.0 Beta 2, 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 Preview with SOA (formerly NetBeans Enterprise Pack) which is part of the SDK tools bundle.

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.

Java Platform, Standard Edition Development Kit 6 Update 1

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 Preview

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

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
64-bit Sun Solaris 10 (SPARC, x86) 512 MB 512 MB 250 MB free 500 MB free Java SE 5 and 6
Red Hat Enterprise Linux 3.0 U1, 4.0 512 MB 1 GB 250 MB free 500 MB free Java SE 5 and 6
Windows Server 2000 SP4+
Windows 2000 Advanced Server SP4+
Windows Server 2003
Windows XP Pro SP1+
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:
  • Application Server Release Notes
  • Java BluePrints Release Notes
  • Sun Web Developer Pack Release Notes
  • Open ESB Release Notes
  • Portlet Container 1.0 Release Notes
  • Access Manager Release Notes
  • Java EE 5 Tools Bundle Release Notes

    ID Description / Workaround
    6551017 Open ESB Java Application Platform SDK installations: JBI components installer recursively delete addons directory during uninstallation.

    Problems arise if the Open ESB component is selected for configuration along with other SDK components.

    Workaround: During Java Application Platform SDK installation, if OpenESB is selected for configuration in addition to other SDK components, Do not uninstall OpenESB using the Update Center Installed Software tab. Uninstalling OpenESB in this manner deletes files needed by other components affecting their functioning.
    6548198 Application Server: Unable to login to the Application Server Administration Console in the Cluster Profile after some operations.

    Workaround: Restart the server using the command-line interface, then log into the Admin Console.
    6546660 SWDP: mailblogger sample does not work with blogapps server.

    A wrong classpath error message displays. When the classpath is modified to make the correction, the following error message displays:
    Exception in thread "main"
     java.lang.NoClassDefFoundError: 
    org/jaxen/JaxenException
       at java.lang.Class.forName0(Native Method)
       at java.lang.Class.forName(Class.java:169)
       at org.jdom.xpath.XPath.newInstance(XPath.java:126)
       at org.blogapps.mailblogger.MailBlogger
       .getString(MailBlogger.java:140)
       at org.blogapps.mailblogger.MailBlogger
       .InitFromXml(MailBlogger.java:122)
       at org.blogapps.mailblogger.MailBlogger
       .main(MailBlogger.java:64)              
    Workaround: None; will update through the Update Center.
    6546654 SWDP: Filecaster samples needs to be constructed to work with the Application Server.

    Workaround: None; will update through the Update Center.
    6546647 SWDP: Crossposter sample does not work.

    A wrong classpath error message displays. When the classpath is modified to make the correction, the following error message displays:
    + java -classpath
    .:lib/commons-codec-1.3.jar:lib/
    commons-collections.jar:lib/
    commons-httpclient-3.0.1.jar:lib/
    commons-lang-2.0.jar:lib/
    crossposter.jar:lib/feedparser.jar:lib/
    jdom-1.0.jar:lib/
    rome-0.9.jar:lib/rome-propono-0.5.jar:lib/
    ws-commons-util-1.0.1.jar:lib/
    xmlrpc-client-3.0.jar:lib/xmlrpc-common-3.0.jar 
    org.blogapps.crossposter.CrossPoster
    CrossPoster for Java
    Exception in thread "main"
     java.lang.NoClassDefFoundError: 
    org/jaxen/JaxenException
       at java.lang.Class.forName0(Native Method)
       at java.lang.Class.forName(Class.java:169)
       at org.jdom.xpath.XPath.newInstance(XPath.java:126)
       at org.blogapps.crossposter.CrossPoster
       .getString(CrossPoster.java:141)
       at org.blogapps.crossposter.CrossPoster
       .initFromXml(CrossPoster.java:119)
       at org.blogapps.crossposter.CrossPoster
       .main(CrossPoster.java:56)
    

    Workaround: None; will update through the Update Center.
    6546645 SWDP: Feedposter sample does not work.

    The following error message displays:
      ./FeedPoster.sh FeedPoster.config.xml
    Exception in thread "main"
     java.lang.NoClassDefFoundError: 
    org/jaxen/JaxenException
       at java.lang.Class.forName0(Native Method)
       at java.lang.Class.forName(Class.java:169)
       at org.jdom.xpath.XPath.newInstance(XPath.java:126)
       at org.blogapps.feedposter.FeedPoster
       .getString(FeedPoster.java:163)
       at org.blogapps.feedposter.FeedPoster
       .initFromXml(FeedPoster.java:146)
       at org.blogapps.feedposter.FeedPoster
       .main(FeedPoster.java:60)
    


    Workaround: None; will update through the Update Center.
    6546640 SWDP: PlanetTool sample does not work.
    Workaround: None; will update through the Update Center.
    6546633
    100634 Issuezilla
    Open ESB: Cannot add an external WSDL document.
    This problem arises when importing an external WSDL and resolving the imported resources (e.g. the XML schema definitions).

    Workaround:To resolve the problem, modify the original WSDL to include the XSDs inline.
    Here is an example:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
        xmlns="http://schemas.xmlsoap.org/wsdl/"
        xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         name="SynchronousSample"
        targetNamespace="http://localhost/
        SynchronousSample/SynchronousSample"
        xmlns:tns="http://localhost/SynchronousSample/
        SynchronousSample" 
        xmlns:ns="http://xml.netbeans.org/schema/
        SynchronousSample" 
        xmlns:plink=
        "http://docs.oasis-open.org/wsbpel/2.0/plnktype">
      <types>
        <xsd:schema targetNamespace="http://localhost/
        SynchronousSample/SynchronousSample">
        <xsd:import namespace="http://xml.netbeans.org/
        schema/SynchronousSample" 
        schemaLocation="SynchronousSample.xsd"/>
             / / this is the problem.
        </xsd:schema>
      </types>
      <message name="requestMessage">
          <part name="inputType" element="ns:typeA"/>
      </message>
      <message name="responseMessage">
          <part name="resultType" element="ns:typeA"/>
      </message>
      <portType name="portType1">
         <operation name="operation1">
            <input name="input1"
             message="tns:requestMessage"/>
            <output name="output1"
             message="tns:responseMessage"/>
          </operation>
      </portType>
      <binding name="binding1" type="tns:portType1">
         <soap:binding transport=
         "http://schemas.xmlsoap.org/soap/http"
          style="document"/>
         <operation name="operation1">
         <input name="input1">
         <soap:body use="literal"/>
         </input>
         <output name="output1">
         <soap:body use="literal"/>
         </output>
         </operation>
     </binding>
        <service name="service1">
           <port name="port1" binding="tns:binding1">
             <documentation/>
             <soap:address location=
             "http://localhost:18181/SynchronousSample"/>
           </port>
        </service>
        <plink:partnerLinkType name="partnerlinktype1">
        <plink:role name="partnerlinktyperole1"
         portType="tns:portType1"/>
        </plink:partnerLinkType>
    
    </definitions>
    

    Modify this WSDL to:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
       xmlns="http://schemas.xmlsoap.org/wsdl/"
       xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
       xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
       xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        name="SynchronousSample"
       targetNamespace="http://localhost/
       SynchronousSample/SynchronousSampleTest"
       xmlns:tns="http://localhost/SynchronousSample/
       SynchronousSampleTest"
       xmlns:ns="http://xml.netbeans.org/schema/
       SynchronousSampleTest"
       xmlns:plink="http://docs.oasis-open.org/
       wsbpel/2.0/plnktype">
       <types>
        <xsd:schema xmlns:xsd=
        "http://www.w3.org/2001/XMLSchema"
        // making the schema definition inline
        targetNamespace="http://xml.netbeans.org/schema/
        SynchronousSampleTest"
        xmlns:tns="http://xml.netbeans.org/schema/
        SynchronousSampleTest"
        elementFormDefault="qualified">
        <xsd:complexType name="simpleProcess">
        <xsd:sequence>
        <xsd:element name="paramA" type="xsd:string"/>
        </xsd:sequence>
        </xsd:complexType>
        <xsd:element name="typeA"
         type="tns:simpleProcess"/>
        </xsd:schema>
        </types>
        <message name="requestMessage">
          <part name="inputType" element="ns:typeA"/>
        </message>
        <message name="responseMessage">
          <part name="resultType" element="ns:typeA"/>
       </message>
        <portType name="portType1">
          <operation name="operation1">
             <input name="input1"
              message="tns:requestMessage"/>
             <output name="output1"
              message="tns:responseMessage"/>
          </operation>
        </portType>
       <binding name="binding1" type="tns:portType1">
          <soap:binding transport="http://schemas.xmlsoap
          .org/soap/http" style="document"/>
          <operation name="operation1">
          <input name="input1">
          <soap:body use="literal"/>
          </input>
          <output name="output1">
          <soap:body use="literal"/>
          </output>
          </operation>
       </binding>
       <service name="myService">
          <port name="port1" binding="tns:binding1">
          <documentation/>
          <soap:address location=
          "http://localhost:18181/SynchronousSample"/>
          </port>
       </service>
         <plink:partnerLinkType name="partnerlinktype1">
         <plink:role name="partnerlinktyperole1"
          portType="tns:portType1"/>
         </plink:partnerLinkType>
    
    </definitions>
    
    6546145 SWDP: Feedgenerators sample should be constructed to work with the Application Server.

    The following error message displays:
    C:\sun\AppServer91pe\swdp\blogapps\planettool\
    dist\planet-tool>planet-tool.bat
    planet-config.xml
    Exception in thread
     "main" java.lang.NoClassDefFoundError:
    org/apache/commons/logging/LogFactory
      at org.blogapps.planettool
      .PlanetManagerImpl.(PlanetManagerImpl.java:48)
    


    Workaround: None; will update through the Update Center.
    6546138 SWDP: RomeExamples do not work.

    The testdata directory is missing for running the sample. However, when the testdata is provided, the following exception displays:
         run org.blogapps.romeexamples.ParseFeed 
    ..\..\..\testdata/rss_2.0-rssweather.xml 
    Exception in thread
     "main" java.lang.NoClassDefFoundError:
    com/sun/syndication/io/SyndFeedInput
       at org.blogapps.romeexamples.ParseFeed
       .parseFeed(ParseFeed.java:20)
       at org.blogapps.romeexamples.ParseFeed
       .main(ParseFeed.java:16)
    

    Workaround: None; will update through the Update Center.
    6545902 SWDP: wadl2java_yahoo sample does not work.

    The build fails with the following message:
    java.lang.LinkageError: JAXB 2.0 API
    is being loaded from the 
    bootstrap classloader, but this RI (from
    jar:file:/C:/sun/SDK/lib/
    webservices-rt.jar!/com/sun/xml/
    bind/v2/model/impl/ModelBuilder.class)
    needs 2.1 API. 
    Use the endorsed directory mechanism
    to place jaxb-api.jar 
    in the bootstrap classloader. (See 
    http://java.sun.com/j2se/1.5.0/
    docs/guide/standards/)
    
    

    Workaround: None; will update through the Update Center.
    6545641 SWDP: cannot run Blogapps/blogclient sample.

    While following the instructions in the SWDP AtomServer ReadMe, the following error message occurs:
    C:\sun\SDK\samples\swdp\blogapps\
    blogclient\dist\blogclient>
    blogclient.batjava.io.FileNotFoundException: 
    C:\Documents and Settings\dada\
    blogclient.properties 
    (The system cannot find the file specified)
       at java.io.FileInputStream.open(Native Method)
       at java.io.FileInputStream.(FileInputStream.java:106)
       at java.io.FileInputStream.(FileInputStream.java:66)
       at org.blogapps.blogclient.blogclientui.LoginFrame.
       (LoginFrame.java:39)
       at org.blogapps.blogclient.blogclientui
       .LoginFrame$4.run
       (LoginFrame.java:246)
       at java.awt.event.InvocationEvent.dispatch
       (InvocationEvent.java:209)
       at java.awt.EventQueue.dispatchEvent
       (EventQueue.java:597)
       at java.awt.EventDispatchThread
       .pumpOneEventForFilters
       (EventDispatchThread.java:273)
       at java.awt.EventDispatchThread
       .pumpEventsForFilter
       (EventDispatchThread.java:183)
       at java.awt.EventDispatchThread
       .pumpEventsForHierarchy
       (EventDispatchThread.java:173)
       at java.awt.EventDispatchThread.pumpEvents
       (EventDispatchThread.java:168)
       at java.awt.EventDispatchThread.pumpEvents
       (EventDispatchThread.java:160)
       at java.awt.EventDispatchThread.run
       (EventDispatchThread.java:121)
    

    The following error message displays when attempting to login to the Admin Console.
    Exception in thread "AWT-EventQueue-0"
     java.lang.NoClassDefFoundError: 
    org/apache/commons/logging/LogFactory
       at org.blogapps.blogclient.atomclient
       .AtomConnection.
       (AtomConnection.java:50)
       at java.lang.Class.forName0(Native Method)
       at java.lang.Class.forName(Class.java:169)
       at org.blogapps.blogclient.blogclient
       .BlogConnectionFactory.
       createBlogConnection(BlogConnectionFactory.java:66)
       at org.blogapps.blogclient.blogclient
       .BlogConnectionFactory.
       getBlogConnection(BlogConnectionFactory.java:53)
       at org.blogapps.blogclient.blogclientui
       .BlogClientFrame.
       newBlogConnection(BlogClientFrame.java:118)
       at org.blogapps.blogclient.blogclientui
       .BlogClientFrame.
       initBlogClientLib(BlogClientFrame.java:107)
       at org.blogapps.blogclient.blogclientui
       .BlogClientFrame.
       (BlogClientFrame.java:58)
       at org.blogapps.blogclient.blogclientui
       .LoginFrame.
       newBlogClientFrame(LoginFrame.java:237)
       at org.blogapps.blogclient.blogclientui
       .LoginFrame$3.
       run(LoginFrame.java:224)
       at java.awt.event.InvocationEvent
       .dispatch(InvocationEvent.java:209)
       at java.awt.EventQueue.dispatchEvent
       (EventQueue.java:597)
       at java.awt.EventDispatchThread.pumpOneEventForFilters
       (EventDispatchThread.java:273)
       at java.awt.EventDispatchThread.pumpEventsForFilter
       (EventDispatchThread.java:183)
       at java.awt.EventDispatchThread.pumpEventsForHierarchy
       (EventDispatchThread.java:173)
       at java.awt.EventDispatchThread
       .pumpEvents(EventDispatchThread.java:168)
       at java.awt.EventDispatchThread
       .pumpEvents(EventDispatchThread.java:160)
       at java.awt.EventDispatchThread
       .run(EventDispatchThread.java:121)
       

    Workaround: None; will update through the Update Center.
    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: 
    id=form1:jmaki_chart11
    Script: http://easqelx5.red.iplanet.com:4848/
    resources/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.
    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.

    6478989 Access Manager: JSR client provider (validateResponse) is getting invoked after the application validates

    Workaround: In Java EE 5 projects (JAX-WS embedded clients), the interception of JSR196 client provider for "validateResponse" is happening before the JAX-WS SOAP client validates the SOAP message. Will be fixed in next release.
    6475928 On Windows, remove system tray icon during SDK uninstallation.

    Workaround: The SDK uninstaller currently does remove shortcut for tray icon from the Startup menu. Consequently, the tray icon will dissapear if user logs off and back on and the desktop is restarted.
    102389
    Issuezilla
    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.

Java EE SDK Fuels Efficiency - Get it Now

GlassFish AppServer - Get it Now

Download the NetBeans IDE

Getting Started
 
Related Resources
 
Open Project Glassfish