[jira] Updated: (BEANUTILS-307) BeanUtils.setProperty(...) not working for property xValue

2008-02-28 Thread Alexander Koppelhuber (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Koppelhuber updated BEANUTILS-307:


Fix Version/s: (was: 1.8.0)
  Description: 
settings values for a property that has one lower case character at the 
beginning
followed by an upper case character does not work. for example xValue or 
zIndex.
The reason (as far as I found out) is as follows:
Introspector.getBeanInfo() gets the property names from the get/set methods.
In Introspector.getTargetPropertyInfo() the following code creates a 
PropertyDescriptor:
pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)

decapitalize() says when there is more than one character and both the 
first and second characters are upper case, we leave it alone...
which results in the name = XValue for the method getXValue()

so setProperty(...) does not find a descriptor for xValue and cannot call the 
setXValue method

I think this issue is not limited to 1.8 beta but also to earlier versions

  was:
settings values for a property that has one lower case character at the 
beginning
followed by an upper case character does not work. for example xValue or 
zIndex.
The reason (as far as I found out) is as follows:
Introspector.getBeanInfo() gets the property names from the get/set methods.
In Introspector.getTargetPropertyInfo() the following code creates a 
PropertyDescriptor:
pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)

decapitalize() says when there is more than one character and both the 
first and second characters are upper case, we leave it alone...
which results in the name = XValue for the method getXValue()

so setProperty(...) does not find a descriptor for xValue and cannot call the 
setXValue method


 BeanUtils.setProperty(...) not working for property xValue
 

 Key: BEANUTILS-307
 URL: https://issues.apache.org/jira/browse/BEANUTILS-307
 Project: Commons BeanUtils
  Issue Type: Bug
  Components: Bean / Property Utils
Affects Versions: 1.8.0-BETA
 Environment: linux, jdk 1.6, beanutils 1.8 beta
Reporter: Alexander Koppelhuber

 settings values for a property that has one lower case character at the 
 beginning
 followed by an upper case character does not work. for example xValue or 
 zIndex.
 The reason (as far as I found out) is as follows:
 Introspector.getBeanInfo() gets the property names from the get/set methods.
 In Introspector.getTargetPropertyInfo() the following code creates a 
 PropertyDescriptor:
 pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)
 decapitalize() says when there is more than one character and both 
 the first and second characters are upper case, we leave it alone...
 which results in the name = XValue for the method getXValue()
 so setProperty(...) does not find a descriptor for xValue and cannot call 
 the setXValue method
 I think this issue is not limited to 1.8 beta but also to earlier versions

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



[jira] Updated: (BEANUTILS-307) BeanUtils.setProperty(...) not working for property xValue

2008-02-28 Thread Alexander Koppelhuber (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Koppelhuber updated BEANUTILS-307:


Description: 
setting values for a property that has one lower case character at the beginning
followed by an upper case character does not work. for example xValue or 
zIndex.
The reason (as far as I found out) is as follows:
Introspector.getBeanInfo() gets the property names from the get/set methods.
In Introspector.getTargetPropertyInfo() the following code creates a 
PropertyDescriptor:
pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)

decapitalize() says when there is more than one character and both the 
first and second characters are upper case, we leave it alone...
which results in the name = XValue for the method getXValue()

so setProperty(...) does not find a descriptor for xValue and cannot call the 
setXValue method

I think this issue is not limited to 1.8 beta but also to earlier versions

  was:
settings values for a property that has one lower case character at the 
beginning
followed by an upper case character does not work. for example xValue or 
zIndex.
The reason (as far as I found out) is as follows:
Introspector.getBeanInfo() gets the property names from the get/set methods.
In Introspector.getTargetPropertyInfo() the following code creates a 
PropertyDescriptor:
pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)

decapitalize() says when there is more than one character and both the 
first and second characters are upper case, we leave it alone...
which results in the name = XValue for the method getXValue()

so setProperty(...) does not find a descriptor for xValue and cannot call the 
setXValue method

I think this issue is not limited to 1.8 beta but also to earlier versions


 BeanUtils.setProperty(...) not working for property xValue
 

 Key: BEANUTILS-307
 URL: https://issues.apache.org/jira/browse/BEANUTILS-307
 Project: Commons BeanUtils
  Issue Type: Bug
  Components: Bean / Property Utils
Affects Versions: 1.8.0-BETA
 Environment: linux, jdk 1.6, beanutils 1.8 beta
Reporter: Alexander Koppelhuber

 setting values for a property that has one lower case character at the 
 beginning
 followed by an upper case character does not work. for example xValue or 
 zIndex.
 The reason (as far as I found out) is as follows:
 Introspector.getBeanInfo() gets the property names from the get/set methods.
 In Introspector.getTargetPropertyInfo() the following code creates a 
 PropertyDescriptor:
 pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)
 decapitalize() says when there is more than one character and both 
 the first and second characters are upper case, we leave it alone...
 which results in the name = XValue for the method getXValue()
 so setProperty(...) does not find a descriptor for xValue and cannot call 
 the setXValue method
 I think this issue is not limited to 1.8 beta but also to earlier versions

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



[jira] Updated: (BEANUTILS-307) BeanUtils.setProperty(...) not working for property xValue (see description for reason)

2008-02-28 Thread Alexander Koppelhuber (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Koppelhuber updated BEANUTILS-307:


Summary: BeanUtils.setProperty(...) not working for property xValue (see 
description for reason)  (was: BeanUtils.setProperty(...) not working for 
property xValue)

 BeanUtils.setProperty(...) not working for property xValue (see description 
 for reason)
 -

 Key: BEANUTILS-307
 URL: https://issues.apache.org/jira/browse/BEANUTILS-307
 Project: Commons BeanUtils
  Issue Type: Bug
  Components: Bean / Property Utils
Affects Versions: 1.8.0-BETA
 Environment: linux, jdk 1.6, beanutils 1.8 beta
Reporter: Alexander Koppelhuber

 setting values for a property that has one lower case character at the 
 beginning
 followed by an upper case character does not work. for example xValue or 
 zIndex.
 The reason (as far as I found out) is as follows:
 Introspector.getBeanInfo() gets the property names from the get/set methods.
 In Introspector.getTargetPropertyInfo() the following code creates a 
 PropertyDescriptor:
 pd = new PropertyDescriptor(decapitalize(name.substring(3)),..)
 decapitalize() says when there is more than one character and both 
 the first and second characters are upper case, we leave it alone...
 which results in the name = XValue for the method getXValue()
 so setProperty(...) does not find a descriptor for xValue and cannot call 
 the setXValue method
 I think this issue is not limited to 1.8 beta but also to earlier versions

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