[
https://issues.apache.org/jira/browse/BEANUTILS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580393#action_12580393
]
Paul Benedict commented on BEANUTILS-311:
-----------------------------------------
I wouldn't leave this behavior, undefined. This is my suggestion (method names
are just examples):
Add a new method called populateRealProperties which contains the logic to
actually populate the real properties. Delegates to an overrideable method to
perform custom logic if necessary.
public void populateRealProperties(....) {
// maybe real logic will go here one day
postProcessRealProperties(); // extra hook
}
> DynaBean variables are evaluated before member variables.
> ---------------------------------------------------------
>
> Key: BEANUTILS-311
> URL: https://issues.apache.org/jira/browse/BEANUTILS-311
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
> Affects Versions: 1.8.0-BETA
> Reporter: Ivan Popov
>
> Hi,
> I have a class that is a DynaBean (extends LazyDynaBean) and that has some
> member variables, in addition to those of the DynaBean.
> It seems as if dynaBean variables are evaluated first, and as the property to
> evaluate is a member variable and not a dynaBean one,
> it returns a NestedNullException.
> Regards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
