[overlord-commits] Overlord SVN: r630 - cdl/trunk/distribution/src/main/release.

[overlord-commits at lists.jboss.org]

Author: objectiser
Date: 2009-05-01 12:09:03 -0400 (Fri, 01 May 2009)
New Revision: 630

Modified:
   cdl/trunk/distribution/src/main/release/ReleaseNotes.txt
Log:
added MaxPermSize param requirement to installation section of getting started guide, and more information in the release note

Modified: cdl/trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- cdl/trunk/distribution/src/main/release/ReleaseNotes.txt	2009-05-01 15:36:26 UTC (rev 629)
+++ cdl/trunk/distribution/src/main/release/ReleaseNotes.txt	2009-05-01 16:09:03 UTC (rev 630)
@@ -1,9 +1,9 @@
-Overlord CDL 1.0-M1
+Overlord CDL 1.0-M2
 ===================
 
 See the README.txt for more information about the Overlord CDL release.
 
-This is the initial release of the CDL capabilities within the Overlord
+This is the second release of the CDL capabilities within the Overlord
 "SOA Governance" project. Additional information will be made available
 on the Overlord website (http://www.jboss.org/overlord/). Free free to post
 questions to the User forum, or raise issues against the SOAG component
@@ -13,11 +13,28 @@
 considered an alpha version only, and subject to change in future
 releases. Its inclusion within this release is intended to enable the
 community to experiment with the approach and hopefully provide feedback
-that can be used to guide the direction of this capability.
+that can be used to guide the direction of this capability.
+
+This "conversation aware" mechanism in M1 required state information to be
+persisted for each service instance, and used by subsequent invocations of
+the same service instance to understand its context within a business
+transaction. However this has added a significant overhead in the implementation
+and execution of the service. Therefore this M2 release introduces a lighter
+weight approach. The previous M1 approach is still available and referred to
+as the 'stateful' approach, whilst the new approach is referred to as
+'stateless'. As the name suggests, this new approach does not require the
+service to persist and use state information. The only requirement is that
+it uses a few custom ESB actions that enable the behaviour of the service
+to be inferred and used to check for conformance against a choreography
+description.
+
+The same examples are available in both stateful and stateless approaches,
+to enable comparison between the jboss-esb.xml definitions for each service.
+Feedback on both approaches would be appreciated.
 
 Overlord-CDL Development Team
 
 ------------------------------------------------------------------------
 
 The current list of outstanding problems or tasks can be obtained from
-the Overlord JIRA system at: https://jira.jboss.org/jira/browse/SOAG
\ No newline at end of file
+the Overlord JIRA system at: https://jira.jboss.org/jira/browse/SOAG