I'll take another look. I thought I understood how it worked, and it
did funtion just adding that value, so I'm not sure its exactly the same
as I've suggested.
I did try to look at the code, but to be honest it was late, and my
brain wasn't getting around it. I'll have to try that again. Possibly
tonight.
Thanks very much for the help though.
-Kevin
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.
