========================================================================================
Release Notes - WebSphere Application Server Feature Pack for Web 2.0 v1.0 Fix Pack 2
========================================================================================

================================
ACCESSING PRODUCT DOCUMENTATION
================================

In addition to the documentation provided with the Web 2.0 Feature Pack, other documentation
can be found at these locations:

    * IBM Information Center : http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/welc_newinreleaseweb20fp.html
    * Dojo Campus Docs : http://docs.dojocampus.org/
    * Dojo Campus : http://www.dojocampus.org
    * IBM Red Book "Building Dynamic Ajax Applications Using WebSphere Feature Pack for Web 2.0" :
      http://www.redbooks.ibm.com/abstracts/sg247635.html
    * IBM Blog : http://www.ibm.com/developerworks/blogs/page/webtwooh

================================
WHAT'S NEW
================================

RPCAdapter

    * Highlights:
          o RPCAdapter supports access to more flexible set data types when accessing data through the
            support for subclass conversion.
          o Fixed a buffer corruption error when concurrent XML transformation occurs.

AjaxProxy

    * Highlights:
          o The proxy allows for pattern matching of the mime-type in the proxy-config.xml. You
            might use a regular expression if you intend to accept a range of mime-type values.
          o URL normalization has been added. As an example, the user passes in
            http://www.ibm.com/../a/../b then the proxy will normalize the request to
            http://www.ibm.com/a/b
          o Added a security comment to the proxy-config.xml that notes to remove the generic
            http and https from the context path since it's intended for development and not
            production deployment.
          o The Ajax proxy no longer cache's cookies. The behavior remains the same that if a
            user specifies a cookie policy, only the allowed cookies with the specified name are
            allowed to pass through. If no cookie policy is specified, then all cookies are
            allowed to pass through the proxy.
          o Fixed a dangling '=' when processing domino values parameters.

IBM Extensions to Dojo 1.3

    * The IBM extensions for ibm_gauge, ibm_atom, and ibm_opensearch have been donated and are
      available in dojox/widget, dojox/atom/, and dojox/data. The previous IBM Extensions are
      still available, but have been deprecated. IBM will be working with the Dojo community to
      continue to enhance the function in the Dojo Toolkit.

The Dojo Toolkit, version 1.3

    * Highlights:
          o Over 1000 bugs fixed since the Dojo Toolkit, version 1.1
          o Extensive performance improvements on modern browsers as reported on Ajaxian:
                + http://ajaxian.com/archives/taskspeed-more-benchmarks-for-the-libraries-and-browsers
          o Microsoft Internet Explorer 8 support.
          o Google Chrome support
          o Safari 3.1 support.
          o New Dojox Grid widget (introduced in The Dojo Toolkit 1.2).
                + Simplified both programmatic and declarative instantiation.
                + Improved layout and behavior consistency on all the supported browsers
                + Improved accessibility support.
                + Drag and Drop columns.
                + Note: The older grid is still provided for backwards compatibility and remains
                  in its old namespace, dojox.Grid. Its internal classes moved to dojox.grid.compat.
                + Note: Transitioning to the new grid will require updates to your application. See
                  the dojox.Grid references in: http://www.dojotoolkit.org/book/dojo-1-2-release-notes
                  and http://www.dojotoolkit.org/book/dojo-1-3-release-notes for more details.
    * Improved community documentation:
          o Community examples and tutorials: http://www.dojocampus.org/
          o Documentation with inline examples: http://docs.dojocampus.org/
          o API documentation: http://api.dojotoolkit.org/jsdoc/dojo

    * Full Community Release notes:
          o 1.1 to 1.2 release notes: http://www.dojotoolkit.org/book/dojo-1-2-release-notes
          o 1.2 to 1.3 release notes: http://www.dojotoolkit.org/book/1-3-release-notes

Samples:

    * All samples upgraded to use the Dojo Toolkit 1.3.

JSON4J:

    * Performance improvement on deserializing JSON formatted text.
    * JSON.parse() API added that will return the appropriate JSONArtifact (JSONObject
      or JSONArray), based on the input.

MessagingService

    *  Upgraded Pubsub engine to work with default json encoding of dojo 1.2

Developer's Guide:

    * Updated examples to Dojo 1.3. The layout examples now make use of
      dijit.layout.BorderContainer.

Web Messaging Service

    *  A new JSON transport is now the default Bayeux communication transport in
      Dojo 1.3. APAR PK81108 allows the Web messaging service to work with the new JSON
      transport.
          o The following errors occur when using the Bayeux JSON transport and a WebSphere
            Application Server installation without PK81108 installed:
                + Bayeux handshake response returned from server: [ {"error":"400::The request could
                  not be recognized by the server.","successful":false,"channel":"\/meta \/handshake"}]
                + In server's error logs: "CWPSB1314W: Bayeux error 400 occurred when processing a
                  Bayeux request for channel with arguments  in Web messaging definition
                  quotestreamer.war_WebMsgServlet"
          o A workaround for this problem is available. You must change the following statement
            in your Dojo client code:
            dojo.require("dojox.cometd");
            to
            dojo.require("dojox.cometd.longPollTransportFormEncoded");