Hi Jesse,
Jesse Kuhnert wrote:
I think the problem with this approach is that the For component has
no way of uniquely identifying your list values.
I would try using the keyExpression or converter parameters of the For
component to do this instead.
http://tapestry.apache.org/tapestry4.1/components/general/for.html
Thanks for the pointers, but I'm still having problems, using either a
custom converter or a keyExpression (using "toString()"). As I
understand it either of these methods rely on there being a single
reference to the object that doesn't change between requests. This
obviously doesn't exist for value objects.
What I'm finding confusing is that this looks to me just like the
example in the charts pane of the tapestry workbench demo; there a list
of PlotValues is edited without keyExpresssion or a converter. Why is
this different?
Would a reasonable hack be to bind the value of the text field input to
a property with a concrete setter that used the @For index to build the
new list items manually?
Thanks,
jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
