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

[sk...@apache.org]

Author: skitching
Date: Wed Oct  8 05:44:16 2008
New Revision: 702850

URL: http://svn.apache.org/viewvc?rev=702850&view=rev
Log:
Add info about new Conversation.enter check.

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=702850&r1=702849&r2=702850&view=diff
==============================================================================
--- myfaces/orchestra/trunk/core/RELEASE-NOTES.txt (original)
+++ myfaces/orchestra/trunk/core/RELEASE-NOTES.txt Wed Oct  8 05:44:16 2008
@@ -70,6 +70,16 @@
 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.
 
+=== Invocation of Beans in Invalidated Conversations Now Detected ===
+
+Previously if a non-scoped-proxy referenced a bean in a conversation that had been deleted, then
+invoking that proxy would not report an error - though things would probably not work, as all the
+other beans in the conversation have been removed. Now an IllegalStateException gets thrown if this
+ever happens. It is pretty difficult to actually get into this situation without using the
+Conversation.bind(Object) method (which was added in the 1.3 release) so this is unlikely to affect
+existing code. And if it does, that code was probably broken anyway. 
+
+
 == New Features
 
 === Binding of arbitrary beans ===