In my case an encoder would be useless, because the entities are new.
Their primary key would be null.
a.
tapestryphoto wrote:
My understanding is the "additional configuration" is in using an
encoder. If you have simple serializable objects (like I do) then it
should just encode them automagically in the form. If you have complex
objects then you need to write an encoder so only, say, object ids are
encoded in the form.
p.
Quoting Andy Pahne <[EMAIL PROTECTED]>:
It should work somehow, at least the documentation says so:
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/Loop.html
(at the very end of the page).
Quote "Tapestry form control element components (TextField, etc.) work
inside loops. However, some additional configuration is needed to make
this work efficiently. "
Unfortunatly it does not say what "additional configuration" is needed
to make that work.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
