I'm not sure I understand your problem, but I'll try to explain what I can :
If your problem is that in fields in a table, only the first field is updated, then this has nothing to do with forceIndexFormula, and it might very well be a bug. I had a similar problem, but I didn't take the time to dig into it. Another probable bug is that the table content is only updated on the second request. This too might be a bug, and I didn't had time to check it either.
The problem solved by forceIndexFormula is when the backend data can change between requests (order changes, or data insertion/deletion). It makes sure that the right row is updated. This is explained a the bottom of the t:dataTable doc :
http://myfaces.apache.org/tomahawk/extDataTable.html
HTH
Sylvain.
On Wed, 2005-08-31 at 08:53 +0200, Martin Marinschek wrote:
Kevin, I am trying to get Sylvain involved in this to explain forceIndexFormula better (hint: this should be in the documentation ;) - but I believe that his solution is somewhat similar to your suggestion! Particularly, you just get the id of the data row as part of the client-id in your action, and it is your responsibility then to fetch this row! regards, Martin On 8/30/05, Kevin Galligan <[EMAIL PROTECTED]> wrote: > My brain is very struts centric as well. There's some things I like > about the JSF model too though. Thats why I'm probably landing > somewhere in between. > > I generally avoided session scoping anything that didn't need to be, > which I guess is my big reservation with JSF. I know exactly what you > mean with the lazy list in the form. You do have some extra effort > involved, like building the property string on the input objects and > tracking the id's in a hidden input component, but there's not as much > going on "behind the curtain" either. > > I think that's enough for today though... > > Rick Reumann wrote: > > On 8/30/05, Kevin Galligan <[EMAIL PROTECTED]> wrote: > > > > > >>I think updating several rows at the same time, which might require > >>local copies of the data, and just linking are two different things. > >>They might need two different components. > > > > > > With Struts this was a piece of cake. Your ActionForm has a bean > > property that is a List of the objects you want to update (Helps if > > it's a LazyList if not using session scope), and when your form > > submits BeanUtils (in the background) simply copies your form objects > > to the List in the Action form. Super simple imo. > > > > The only slightly tricky part is validation, but I always provide a > > manual validation method in my Action classes so this was easy to > > handle. > >
