[
https://issues.apache.org/jira/browse/BEANUTILS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591742#comment-13591742
]
Benedikt Ritter edited comment on BEANUTILS-394 at 3/3/13 1:42 PM:
-------------------------------------------------------------------
Sorry I don't understand what failure you're describing. Can you please provide
example code that shows the failure?
TIA!
Benedikt
was (Author: britter):
Sorry I don't understand what failure you a describing. Can you please
provide example code that shows the failure?
TIA!
Benedikt
> in BeanUtilsBean.setProperty method, a call to
> PropertyDescriptor.getReadMethod should call getWriteMethod. code writing
> mistakes which would issue in incorrect and unexpected result.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BEANUTILS-394
> URL: https://issues.apache.org/jira/browse/BEANUTILS-394
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
> Affects Versions: 1.8.3
> Environment: Windows 7 64bit.
> Reporter: Yi, Han
> Priority: Critical
> Labels: lapsus
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> in edition 1.8.3 of the BeanUtilsBean's setProperty method, line 962, when
> judging if the bean has no writing method, it will return and don't process
> the setting method, what the codes have been written were:
> } else if (key != null) {
> if (descriptor.getReadMethod() == null) {
> if (log.isDebugEnabled()) {
> log.debug("Skipping read-only property");
> }
> return; // Read-only, skip this property setter
> }
> type = (value == null) ? Object.class : value.getClass();
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
