[cvs] expresso commit by lhamel: isMutable, cache access
JCorporate Ltd
jcorp at jcorporate.com
Mon Feb 21 02:26:43 UTC 2005
Log Message:
-----------
isMutable, cache access
Modified Files:
--------------
expresso/expresso-web/expresso/doc:
ChangeLog.xml
Revision Data
-------------
Index: ChangeLog.xml
===================================================================
RCS file: /home/javacorp/.cvs/expresso/expresso/expresso-web/expresso/doc/ChangeLog.xml,v
retrieving revision 1.288
retrieving revision 1.289
diff -Lexpresso-web/expresso/doc/ChangeLog.xml -Lexpresso-web/expresso/doc/ChangeLog.xml -u -r1.288 -r1.289
--- expresso-web/expresso/doc/ChangeLog.xml
+++ expresso-web/expresso/doc/ChangeLog.xml
@@ -5,6 +5,18 @@
<project name="Expresso">
<version name="5.6.1" releaseDate="Not released yet">
<comment>Continued Updates</comment>
+ <new-feature title="isMutable() and access to actual cached items.">
+ <explanation>a new attribute
+ DBObject.isMutable() is now set on cached copies. This attribute is now
+ tested during any set* and update() methods, throwing an exception if the DBObject
+ is marked as immutable. This protects usage of the actual cached items as a read-only source.
+ To provide access to the actual cached, read-only objects, two new methods
+ (one static and one instance method) are available:
+ public DBObject getImmutableObjectFromCache(String keyValues)
+ public static DBObject getImmutableCachedObject(Class dbobjClass, String keyValues)
+ </explanation>
+ <contributor>Larry Hamel</contributor>
+ </new-feature>
<bug-fix title="After being added to the response, ControllerElement's were no longer serializable">
<explanation>Made ServletControllerResponse serializable. Any ControllerElement, after being added to the response, became unserializable. This is because the response being stored in ControllerElement was actually an instance ServletControllerResponse, not ControllerResponse (which is serializable).
</explanation>
More information about the cvs
mailing list