svn commit: r704401 - /myfaces/orchestra/trunk/core/RELEASE-NOTES.txt

[sk...@apache.org]

Author: skitching
Date: Tue Oct 14 02:10:50 2008
New Revision: 704401

URL: http://svn.apache.org/viewvc?rev=704401&view=rev
Log:
Add info about SpringBasicFrameworkAdapter bug. Other minor changes.

Modified:
    myfaces/orchestra/trunk/core/RELEASE-NOTES.txt

Modified: myfaces/orchestra/trunk/core/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/myfaces/orchestra/trunk/core/RELEASE-NOTES.txt?rev=704401&r1=704400&r2=704401&view=diff
==============================================================================
--- myfaces/orchestra/trunk/core/RELEASE-NOTES.txt (original)
+++ myfaces/orchestra/trunk/core/RELEASE-NOTES.txt Tue Oct 14 02:10:50 2008
@@ -28,7 +28,7 @@
 some changes in core classes that will affect people who have modified the internal
 implementation of Orchestra.
 
-* ConversationManager.getConverationContext(Long) was previously protected and is now public. This
+* ConversationManager.getConversationContext(Long) was previously protected and is now public. This
   is theoretically a binary-incompatible change as existing subclasses that override the method using
   scope of protected will now fail to compile. However it is extremely unlikely that anyone has done this.  
   Commit: r702065 
@@ -45,9 +45,13 @@
    Weblets when cookies are disabled; with that combination a separate Session was being created for each
    weblet request. See r687072.
  
+ * Fix SpringBasicFrameworkAdapter.getBean(String), which threw an exception if the bean did not exist
+   instead of simply returning null.
+
 == Known Issues
 
- * Orchestra still does not work with Portlets (ORCHESTRA-17, ORCHESTRA-22)
+ * As far as we know, Orchestra still does not work with Portlets (ORCHESTRA-17, ORCHESTRA-22). At least,
+   problems have been reported against earlier versions and no-one has tested this release with Portlets.
 
 == Major Changes
 
@@ -68,7 +72,8 @@
 
 This does introduce some possible behavioural changes. Previously if a conversation was only accessed
 by components which can be toggled between rendered and not-rendered then when the components were
-not rendered the conversation would be discarded; now it is preserved.
+not rendered the conversation would be discarded; ie hiding/showing a component would reset it.
+Now the conversation is preserved, ie hiding/showing a component does not reset its state.
 
 === Invocation of Beans in Invalidated Conversations Now Detected ===