RiftSaw 2.1.0.Final
===================

This is the final release for RiftSaw version 2.1. The summary of the main changes
between 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

- 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
=================

This is a bug fix release.

The main change with this release is the migration to the pure JPA persistence layer
from the native Hibernate layer. Moving to the JPA persistence layer has resolved a 
number of long standing bugs.

Hibernate is still used as the JPA provider. However to align the database schema with
the ODE community project, it has been necessary to make some schema changes.
Therefore it will be necessary to drop the current database (or simply
remove the $AS/server/default/data folder). This JPA work is being contributed back
to the ODE project, and should be available in ODE 1.4. 

The other main change is the simplification of the ESB examples, both in terms of how
they are run, and also in terms of their complexity. Previously the primary ESB/Riftsaw
example was too complex, making it difficult to use and follow. Instead this has been
replaced by a couple of new simpler examples that demonstrate the specific integration
points between JBossESB and RiftSaw.

The detailed report for this release can be found at:
https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12314933


RiftSaw 2.1.0.CR1
=================

This is primarily a bug fix release, with additional support for configuring the
Apache CXF web service endpoints used by a BPEL process.

WS-Security features, supported by Apache CXF, can now be configured for RiftSaw when the
jboss-cxf Web Service stack is installed. The User Guide provides information on how to
include the CXF based configuration with the BPEL deployment, and there are some quickstarts
available to demonstrate username and digital signature authentication.

JAX-WS handlers can now be installed to intercept/observe messages sent and returned from
the web service representing a BPEL process.

The version of ODE used by RiftSaw has been updated to ODE 1.3.4.

NOTE: Database schema changes occurred when moving to the ODE 1.3.4 release. If you have
a previous version of RiftSaw installed, then you will need to drop the existing tables
(or delete the database), before installing and running this version of RiftSaw.

The detailed report for this release can be found at:
https://jira.jboss.org/secure/ReleaseNote.jspa?projectId=12310843&version=12314753


RiftSaw 2.0.0.Final
===================

This is the final release of RiftSaw 2.0.0 - the JBoss BPEL server.

Known issues:

RIFTSAW-184,152,173 - all appear to be directly or indirectly related to problems 
	with the ODE simple scheduler implementation, and similar problems have been 
	replicated on ODE running in a tomcat environment. In the next release of RiftSaw,
	this scheduler will be replaced by one that can support clustering, and therefore
	should overcome these issues.
	
RIFTSAW-186 - an unusual timing issue where the ODE engine removes the process instance
	before the final response message has been sent. There appears to be some form of
	synchronization issue in the ODE engine, but only occurs under very specific
	circumstances.
	
RIFTSAW-192 - the webservice_esb_bpel fails to complete due to an issue with an ESB service
	failing to send a notification back to the active BPEL process. This leaves the
	BPEL process in a 'RUNNING' state within the console.

The detailed report for this release can be found at:
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12314587&styleName=Html&projectId=12310843&Create=Create


RiftSaw 2.0-CR2
===============

This is the second candidate release of RiftSaw 2.0 - the JBoss BPEL server.

This release is a mainly bug fix release, but we also do enhancements on the UDDI features and updated our admin console
into 2.0.1 version, which is the Errai based BPM console. In the database support area, we now support the
HSQL, MySQL, Postgres, Oracle(10g) and SqlServer. For the web service stack, it also fully supports the jbossws-cxf 3.2.2.GA now. 

The detailed report for this release can be found at:
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12314266&styleName=Html&projectId=12310843&Create=Create


RiftSaw 2.0-CR1
===============

This is the first candidate release of RiftSaw 2.0 - the JBoss BPEL server.

This release provides full support for jbossws, as a replacement Web Service stack,
a new GWT based admin console, and database support for HSQL, MYSQL and Postgres.

The detailed report for this release can be found at:
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12314239&styleName=Html&projectId=12310843&Create=Create

Known Issues:

RIFTSAW-127 - RiftSaw currently does not support binding SOAP header elements to WSDL message
parts, as a mechanism for enabling a BPEL process to access the SOAP header. However ODE provides
an extension mechanism to reference a SOAP header from the BPEL process, using the
'header' attribute on the copy construct.




RiftSaw 2.0-M2
==============

This is the second milestone release of RiftSaw 2.0 - the JBoss BPEL server.

The main purpose of this release is to provide early access to the JBossWS integration
and new GWT based admin console. The JBossWS integration replaces the Axis2
functionality provided in 2.0-M1.

The detailed report for this release can be found at:
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313779&styleName=Html&projectId=12310843&Create=Create

Known Issues:

RIFTSAW-10 - Migrate from Axis2 to JBossWS

Most of the functionality has been implemented. The remaining issues relate to a BPEL
process returning a fault (RIFTSAW-91) and where a BPEL process has a WSDL interface that
imports other files (e.g. xsd or wsdl) (RIFTSAW-113).


RIFTSAW-111 - GWT/BIRT related exceptions

Some GWT and BIRT related exceptions occur when the server is started. These can
be ignored.


Database support

There are a number of database related issues. We are investigating moving from
the Hibernate to JPA based DAO implementation for ODE, to help resolve some of these issues
(RIFTSAW-115). At present we would recommend using "hsql" as an in-memory db option,
and mysql as a persistent db.

Known problems include RIFTSAW-73, exception when undeploying BPEL processes using
HSQL, and RIFTSAW-41 where a deadlock can occur when using Derby.


-----------------------------------------------------------------------------------------------

RiftSaw 2.0-M1
==============

This is the first milestone release of RiftSaw 2.0 - the JBoss BPEL server.


