Author: jeff.yuchang
Date: 2010-11-08 06:04:50 -0500 (Mon, 08 Nov 2010)
New Revision: 1090
Modified:
trunk/distribution/src/main/release/ReleaseNotes.txt
Log:
* CR1 release note.
Modified: trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- trunk/distribution/src/main/release/ReleaseNotes.txt 2010-11-08 10:35:34 UTC (rev
1089)
+++ trunk/distribution/src/main/release/ReleaseNotes.txt 2010-11-08 11:04:50 UTC (rev
1090)
@@ -1,3 +1,31 @@
+RiftSaw 2.2.0.CR1
+==================
+
+This is the first release candidate for the 2.2.0 release series.
+
+In this release, we've made a great improvements on the bpel console. With the new
version,
+we've made a new structure and the look&feel of the console. Meanwhile, by
enabling the logging
+in deploy.xml file, admins are able to see execution path of process instances in
console, also
+known as 'visual instance flow'.
+
+secondly we've used the jboss cache as our cache provider in the RiftSaw clustering
environment.
+Admins can log in any node of bpel console to make the process retire/activate, it works
fine now under
+the clustering environment.
+
+Other changes include:
+- BPELInvoke supports WS Security and SAML support.
+- Upgrade juddi to 3.0.4 release.
+
+And of course, with a bunch of bugs fixed.
+
+The detailed report for this release can be found at:
+https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12315480
+
+Know issues:
+1. RIFTSAW-198 : CronScheduler is not supporting cluster
+2. RIFTSAW-316 : exception when WSDL service has multiple ports
+
+
RiftSaw 2.2.0.M1
==================