commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eickvonder (JIRA)" <j...@apache.org>
Subject [jira] Created: (BEANUTILS-347) MappedPropertyDescriptor throws an exception after method reference has been garbage collected
Date Wed, 29 Apr 2009 06:11:30 GMT
MappedPropertyDescriptor throws an exception after method reference has been garbage collected
----------------------------------------------------------------------------------------------

                 Key: BEANUTILS-347
                 URL: https://issues.apache.org/jira/browse/BEANUTILS-347
             Project: Commons BeanUtils
          Issue Type: Bug
          Components: Bean / Property Utils
    Affects Versions: 1.8.0
            Reporter: Eickvonder


If a bean contains a method 

setAnyMapped(anyTypeButString,anyType)

without a corresponding getter the first calls to getMappedWriteMethod return the corresponding
method, but if the soft reference to the method has been garbage collected the runtime exception
'Method ... for ... could not be reconstructed - method not found" is thrown.

First of all I think it is a bug that getMappedWriteMethod is not invariant in its behaviour
concerning garbage collection (at least it should not throw an exception in this case), but
secondly I wonder if it is correct at all that constructing a MappedPropertyDescriptor is
possible though the first parameter is not of type String. But this "odd" behaviour is actually
tested within MappedPropertyTestCase.testAnyArgsProperty().

For me I would be fine if either construction of MappedPropertyDescriptor would fail or getMappedWriteMethod
would return null or the method in both cases before and after garbage collection. The only
thing that breaks my app is the exception being thrown as this is not catched within my call
of BeanUtils.populate.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message