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

Apoorva Rais updated STR-3114:
------------------------------

    Description: 
I have a action form which has structure like
FORM_A( attribute1<String>, attribute2<Date>,....., attributeN 
<LinkedHashMap<<String>,<BeanB>>)  ->   where BeanB has its own 
attributes(attributeA, attributeB....)
I get all these data from data service and I am using logic-iterate/jstl tags 
in jsp to display Map attribute of FORM_A. Display part works fine. 
Now the problem is if the user updates ones of the attributes for BeanB  in UI 
(say attributeB, which is a float), the values are not getting populated in 
BeanB. It never says no setter method found for property or anything and it 
doesn't call setter methods as well.

I think the problem is the way it keeps the name is just name of the 
bean-attribute and it doesn't know which attribute goes in which bean on the 
Map. Right now I am using {indexed="true"} property and manually getting those 
values from request and setting those in bean. Can we have one more attribute 
other than indexed which can tell BeanUtils that use index number to determine 
the location of the bean in the collection <assuming or verifying that its a 
ordered collection> and automatically set value for the attributes in the Bean?
This will reduce lot of work for all grid kind of developments when we have a 
ordered/editable list situation. Please let me know if there's already a way to 
do this in struts 1 or struts 2 ?



  was:
I have a action form which has structure like
FORM_A( attribute1<String>, attribute2<Date>,....., attributeN 
<LinkedHashMap<<String>,<BeanB>>)  ->   where BeanB has its own 
attributes(attributeA, attributeB....)
I get all these data from data service and I am using logic-iterate/jstl tags 
in jsp to display Map attribute of FORM_A. Display part works fine. 
Now the problem is if the user updates ones of the attributes for BeanB  in UI 
(say attributeB, which is a float), the values are not getting populated in 
BeanB. I think the problem is the way it keeps the name is just name of the 
bean-attribute and it doesn't know which attribute goes in which bean on the 
Map. Right now I am using {indexed="true"} property and manually getting those 
values from request and setting those in bean. Can we have one more attribute 
other than indexed which can tell BeanUtils that use index number to determine 
the location of the bean in the collection <assuming or verifying that its a 
ordered collection> and automatically set value for the attributes in the Bean?
This will reduce lot of work for all grid kind of developments when we have a 
ordered/editable list situation. Please let me know if there's already a way to 
do this in struts 1 or struts 2 ?




> Form Bean Properties not being set when form is submitted
> ---------------------------------------------------------
>
>                 Key: STR-3114
>                 URL: https://issues.apache.org/struts/browse/STR-3114
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.3.5
>         Environment: MS/UNIX on Tomcat/Weblogic
>            Reporter: Apoorva Rais
>
> I have a action form which has structure like
> FORM_A( attribute1<String>, attribute2<Date>,....., attributeN 
> <LinkedHashMap<<String>,<BeanB>>)  ->   where BeanB has its own 
> attributes(attributeA, attributeB....)
> I get all these data from data service and I am using logic-iterate/jstl tags 
> in jsp to display Map attribute of FORM_A. Display part works fine. 
> Now the problem is if the user updates ones of the attributes for BeanB  in 
> UI (say attributeB, which is a float), the values are not getting populated 
> in BeanB. It never says no setter method found for property or anything and 
> it doesn't call setter methods as well.
> I think the problem is the way it keeps the name is just name of the 
> bean-attribute and it doesn't know which attribute goes in which bean on the 
> Map. Right now I am using {indexed="true"} property and manually getting 
> those values from request and setting those in bean. Can we have one more 
> attribute other than indexed which can tell BeanUtils that use index number 
> to determine the location of the bean in the collection <assuming or 
> verifying that its a ordered collection> and automatically set value for the 
> attributes in the Bean?
> This will reduce lot of work for all grid kind of developments when we have a 
> ordered/editable list situation. Please let me know if there's already a way 
> to do this in struts 1 or struts 2 ?

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

Reply via email to