svn commit: r756387 - /servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt

[gn...@apache.org]

Author: gnodet
Date: Fri Mar 20 09:30:20 2009
New Revision: 756387

URL: http://svn.apache.org/viewvc?rev=756387&view=rev
Log:
Rework the release notes

Modified:
    servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt

Modified: servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt?rev=756387&r1=756386&r2=756387&view=diff
==============================================================================
--- servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt (original)
+++ servicemix/smx4/nmr/trunk/RELEASE-NOTES.txt Fri Mar 20 09:30:20 2009
@@ -21,21 +21,24 @@
   Overview
   --------
 
- This release brings a lot of features, enhancements and bug fixes.  A lot of work has been done to follow more closely
+ ServiceMix NMR 1.0.0 is a brand new JBI container based on OSGi.  A lot of work has been done to follow more closely
  the rules from the JBI 1.0 specification and to have a much better lifecycle processing for various JBI artifacts.
  A new clustering engine has been developped which allows endpoints to be individually clustered, leveraging the
  transparent remoting (communications between two endpoints on different JBI containers) but also load-balancing and
  fail-over.  Other features include the backporting of the auditor package from ServiceMix 3, the integration of the
  transaction manager and a JNDI/OSGi integration.
 
- ServiceMix NMR 1.0.0 is a brand new JBI container based on OSGi.  Most of the applications developped for ServiceMix 3
- can be deployed onto this container, however, due to the OSGi layer underneath, some classloading related issues may
- arise when migrating an application from ServiceMix 3 because both containers do not behave the same way.  Another major
- change compared to ServiceMix 3 is the changed transactional model which allows the use of transactions for asynchronous
- exchanges: this change will affect your application if you were leveraging the JCA flow in ServiceMix 3.
-
  See the change log below for more informations.
 
+  Migrating from ServiceMix 3
+  ---------------------------
+
+ Most of the applications developped for ServiceMix 3 can be deployed onto this container, however, due to the OSGi
+ layer underneath, some classloading related issues may arise when migrating an application from ServiceMix 3 because
+ both containers do not behave the same way.  Another major change compared to ServiceMix 3 is the changed transactional
+ model which allows the use of transactions for asynchronous exchanges: this change will affect your application if you
+ were leveraging the JCA flow in ServiceMix 3.
+
   Changelog
   ---------