Author: skitching
Date: Sun May 29 00:06:11 2005
New Revision: 178930
URL: http://svn.apache.org/viewcvs?rev=178930&view=rev
Log:
Document PropertyUtils.getNestedProperty and setNestedProperty changes.
Modified:
jakarta/commons/proper/beanutils/trunk/RELEASE-NOTES.txt
Modified: jakarta/commons/proper/beanutils/trunk/RELEASE-NOTES.txt
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/beanutils/trunk/RELEASE-NOTES.txt?rev=178930&r1=178929&r2=178930&view=diff
==============================================================================
--- jakarta/commons/proper/beanutils/trunk/RELEASE-NOTES.txt (original)
+++ jakarta/commons/proper/beanutils/trunk/RELEASE-NOTES.txt Sun May 29
00:06:11 2005
@@ -92,6 +92,8 @@
methods, then you must now override the Map.get and Map.set methods on class X
in order to implement this behaviour.
+Alternatively you may subclass PropertyUtilsBean and override the methods
+getPropertyOfMapBean and setPropertyOfMapBean, thought this is not recommended.
See Bugzilla #23815
@@ -111,9 +113,32 @@
the 1.7.0 release should be checked to make sure that it handles
ConversionException
correctly when invalid data is passed to the convert method.
+See Bugzilla #33839.
CHANGES:
========
+
+PropertyUtilsBean
+-----------------
+Protected methods getPropertyOfMapBean and setPropertyOfMapBean have been added
+to allow users to subclass PropertyUtilsBean and change the way that methods
+getNestedProperty and setNestedProperty behave when encountering an object that
+implements Map. This satisfies a number of bugzilla requests. Note, however,
that
+using this functionality is discouraged; it is better to fix code to work with
+PropertyUtilsBean's default approach.
+
+getNestedProperty/setNestedProperty
+-----------------------------------
+As noted in "IMPORTANT NOTES" section, setNestedProperty now completely ignores
+simple properties on an object that implements Map. This restores the behaviour
+of version 1.5.
+
+When accessing a property of a Map object, an IllegalArgumentException will now
+be thrown if the propertyName is a mapped or indexed expression; formerly, the
+entire string was simply taken literally. Because the old behaviour was
extremely
+unlikely to result in the library doing what the caller expected, this change
is
+not regarded as a backwards incompatibility.
+
ENHANCEMENTS:
=============
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
