You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Endre Jeges (JIRA)" <ji...@apache.org> on 2009/09/11 23:00:57 UTC

[jira] Created: (BEANUTILS-365) MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches

MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches
-----------------------------------------------------------------------

                 Key: BEANUTILS-365
                 URL: https://issues.apache.org/jira/browse/BEANUTILS-365
             Project: Commons BeanUtils
          Issue Type: Improvement
          Components: Bean / Property Utils
    Affects Versions: 1.8.0
         Environment: java 1.6.0_16
            Reporter: Endre Jeges
             Fix For: 1.8.1


In order to gain some performance the MethodUtils.getMatchingAccessibleMethod could cache unsuccessful matches too. In case there is no matching method getMatchingAccessibleMethod returns null after examining the Class but does not store this fact in the cache, the subsequent call to MethodUtils.getMatchingAccessibleMethod will examine the Class again

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


[jira] Updated: (BEANUTILS-365) MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches

Posted by "Francesco Mari (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BEANUTILS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Mari updated BEANUTILS-365:
-------------------------------------

    Attachment: method-utils-cache.patch

The patch contains some modifications to MethodUtils and MethodUtilsTestCase and enables caching for negative matches between methods.

> MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches
> -----------------------------------------------------------------------
>
>                 Key: BEANUTILS-365
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-365
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.0
>         Environment: java 1.6.0_16
>            Reporter: Endre Jeges
>             Fix For: LATER THAN 1.8.3
>
>         Attachments: method-utils-cache.patch
>
>
> In order to gain some performance the MethodUtils.getMatchingAccessibleMethod could cache unsuccessful matches too. In case there is no matching method getMatchingAccessibleMethod returns null after examining the Class but does not store this fact in the cache, the subsequent call to MethodUtils.getMatchingAccessibleMethod will examine the Class again

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


[jira] Updated: (BEANUTILS-365) MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches

Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BEANUTILS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niall Pemberton updated BEANUTILS-365:
--------------------------------------

    Fix Version/s:     (was: 1.8.1)
                   LATER THAN 1.8.1

> MethodUtils.getMatchingAccessibleMethod could cache unsuccesful matches
> -----------------------------------------------------------------------
>
>                 Key: BEANUTILS-365
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-365
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.0
>         Environment: java 1.6.0_16
>            Reporter: Endre Jeges
>             Fix For: LATER THAN 1.8.1
>
>
> In order to gain some performance the MethodUtils.getMatchingAccessibleMethod could cache unsuccessful matches too. In case there is no matching method getMatchingAccessibleMethod returns null after examining the Class but does not store this fact in the cache, the subsequent call to MethodUtils.getMatchingAccessibleMethod will examine the Class again

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