Author: objectiser
Date: 2010-07-15 09:18:20 -0400 (Thu, 15 Jul 2010)
New Revision: 878
Modified:
branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
trunk/distribution/src/main/release/ReleaseNotes.txt
Log:
Updated release notes.
Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15
12:46:27 UTC (rev 877)
+++ branches/RiftSaw-2.1.x/distribution/src/main/release/ReleaseNotes.txt 2010-07-15
13:18:20 UTC (rev 878)
@@ -1,3 +1,46 @@
+RiftSaw 2.1.0.Final
+===================
+
+This is the final release for RiftSaw version 2.1. The summary of the main changes
+from 2.0.0.Final and 2.1.0.Final are:
+
+- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
+
+- UDDI registration and lookup enabled by default (if ESB already deployed with
+UDDI v3 support)
+
+- Migration of persistence layer to a pure JPA approach, enabling any JPA
+compliant persistence provider to be used. RiftSaw uses Hibernate as its
+default JPA provider
+
+- Update from ODE1.3.3 to ODE1.3.4
+
+- ODE project has now been mavenized
+
+- More examples
+
+- Many bug fixes
+
+- Now dependent upon ESB 4.8 or higher (instead of ESB 4.7)
+
+Due to the change from the hibernate native persistence support to a JPA+hibernate
+approach, it is necessary to update to the new schema. Instructions for doing
+this can be found in the Installation Instructions section of the Getting Started Guide.
+
+The detailed report for this release can be found at:
+https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12315122
+
+Known Issues:
+
+RIFTSAW-193 - Wrapped style parameters are currently not supported.
+
+RIFTSAW-238 - If a process definition has multiple versions, one active and the others
retired,
+then undeploying the active version causes the web service associated with the process to
be
+unpublished, even if active process instances still exist for the retired versions.
+
+
+
+
RiftSaw 2.1.0.CR2
=================
Modified: trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 12:46:27 UTC (rev
877)
+++ trunk/distribution/src/main/release/ReleaseNotes.txt 2010-07-15 13:18:20 UTC (rev
878)
@@ -1,3 +1,46 @@
+RiftSaw 2.1.0.Final
+===================
+
+This is the final release for RiftSaw version 2.1. The summary of the main changes
+from 2.0.0.Final and 2.1.0.Final are:
+
+- Support for WS-Security when RiftSaw used in conjunction with JBossWS-CXF
+
+- UDDI registration and lookup enabled by default (if ESB already deployed with
+UDDI v3 support)
+
+- Migration of persistence layer to a pure JPA approach, enabling any JPA
+compliant persistence provider to be used. RiftSaw uses Hibernate as its
+default JPA provider
+
+- Update from ODE1.3.3 to ODE1.3.4
+
+- ODE project has now been mavenized
+
+- More examples
+
+- Many bug fixes
+
+- Now dependent upon ESB 4.8 or higher (instead of ESB 4.7)
+
+Due to the change from the hibernate native persistence support to a JPA+hibernate
+approach, it is necessary to update to the new schema. Instructions for doing
+this can be found in the Installation Instructions section of the Getting Started Guide.
+
+The detailed report for this release can be found at:
+https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12315122
+
+Known Issues:
+
+RIFTSAW-193 - Wrapped style parameters are currently not supported.
+
+RIFTSAW-238 - If a process definition has multiple versions, one active and the others
retired,
+then undeploying the active version causes the web service associated with the process to
be
+unpublished, even if active process instances still exist for the retired versions.
+
+
+
+
RiftSaw 2.1.0.CR2
=================