Author: upul
Date: Mon Jan 14 03:26:57 2008
New Revision: 12220
Log:
release note changes
Modified:
branches/esb/java/1.6/esb/java/modules/distribution/src/main/release/release_notes.txt
Modified:
branches/esb/java/1.6/esb/java/modules/distribution/src/main/release/release_notes.txt
==============================================================================
---
branches/esb/java/1.6/esb/java/modules/distribution/src/main/release/release_notes.txt
(original)
+++
branches/esb/java/1.6/esb/java/modules/distribution/src/main/release/release_notes.txt
Mon Jan 14 03:26:57 2008
@@ -1,4 +1,4 @@
-WSO2 Enterprise Service Bus (ESB), v1.6 - Release Note - 12th January 2008
+WSO2 Enterprise Service Bus (ESB) v1.6 - Release Note - January 2008
===========================================================================
WSO2 ESB is a lightweight, and high performance Enterprise Service Bus (ESB).
@@ -14,7 +14,15 @@
==========================
The 1.6 release
- * Ability to pin a proxy or a task to a list of named ESB servers
+ * Ability to pin a proxy or a task to server instances
+ * Improved error handling in JMS transport
+ * Clustering support for the Cache/Throttle mediators
+ * Maintainance mode support for the HTTP transport
+ * JMX statistics monitoring and management support
+ * New mediators - Callout Mediator
+ * Improved REST/POX support
+ * Annotations support for POJOCommand mediator
+ * Ability to edit UI-less mediators in raw XML
The 1.5 release
* Apache VFS based file transport
@@ -47,43 +55,33 @@
1. WSO2 ESB known issues and limitations deffered for the next release
- ESBJAVA-309 - Unable to view/edit the sequences after clicking on the
"Close" icon of the WSO2
- ESB Sequence Editor window of a sequence in the Integrated Registry
+ ESBJAVA-234 - After clicking on the "Close" button of the "Sequence
Editor" window when adding anonymous sequences to a Proxy Service, the
mediators lost the next time you open the "Sequence Editor" window
- ESBJAVA-308 - Incorrect information logged when executing a configuration
which has a reference
- to a sequence which is exported into the Integrated Registry
+ ESBJAVA-351 - The average response time of "Server Statics" displayed as
NaN under statistics
- ESBJAVA-304 - No options provided to select onReject and onAccept
Sequences as reference keys
- when creating a sequence with the throttle mediator
+ ESBJAVA-268 - Unable to start the sample axis2server.bat on Windows
- ESBJAVA-270 - Unable to load the ESB Management console if JMS is enabled
and the JMS server
- is not started
+ ESBJAVA-373 - [IE] When the wso2-esb.log is about 2MB and when tried to
access System logs using IE, the browser hangs and the CPU usage goes upto
about 50%
- ESBJAVA-268 - Unable to start the axis2server.bat on Windows
+ ESBJAVA-309 - Unable to view/edit the sequences after clicking on the
"Close" icon of the WSO2 ESB Sequence Editor window of a sequence in the
Integrated Registry
- ESBJAVA-258 - ESB hangs during startup if the actual service that a Proxy
Service (created using
- a WSDL Endpoint) points to is down.
+ ESBJAVA-408 - Support improved renaming of files in VFS transport
- ESBJAVA-315 - The cache mediator does not function properly when
configuration is created
- through Administration Console
+ ESBJAVA-76 - Use NIO SSL transport to host admin console instead of Tomcat
- The Aggregator mediator currently does not have a configuration UI with
this release of the ESB
-
2. As the WSO2 ESB 1.6 depends on the Apache Synapse 1.1.1, it inherits the
list of known issues of the
- Apache Synapse 1.1 release listed below
+ Apache Synapse 1.1.1 release listed below
+
+ SYNAPSE-180 - Require the ability to throttle by concurrency within a
cluster
SYNAPSE-174 - The non-blocking http/s transports cannot handle WS-RM
requests
- - Caused by the NIO http/s transport being out of sync with the latest
Sandesh2 codebase
- SYNAPSE-170 - VFS transport listener sample - In the response sent via
email, all tags define the same namespace
- - Caused by an Axis2 Mail transport limitation
+ SYNAPSE-213 - Improve handling of input in XSLTMediator
- SYNAPSE-161 - Can't persuade Rampart to send certificate serial + issuer -
only either BinaryToken or Identity
- - Issue related to Apache Rampart
+ SYNAPSE-211 - Improve performance in XSLTMediator when temporary files are
used
- SYNAPSE-103 - WS-RM not returning response message
- - related to SYNAPSE-174
+ SYNAPSE-212 - XSLTMediator doesn't close/delete temporary files properly
The Synapse JMS implementation supports JMS 1.0.2b, however due to
licensing issues we include
the JMS 1.1 spec JAR from Apache Geronimo (geronimo-jms_1.1_spec-1.1.jar)
instead. If you have
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
