Couldn't you say that of any widget on the form?
The form already acts as an insulation layer between the request and the
backend.
That's true. Probably it's my scarce experience with repeaters that makes me want to double-check what comes back from the form. With simple text fields, it's easier to put enough validation in the form definition, probably. There is some magic in the way CForms handles repeaters and some magic in the way Hibernate handles collection. That's just too much magic ;-).
I can understand that you just need to do "stuff" in between there, but if one doesn't need to do that, you can as well bind directly.
Of course. I was just pointing out why I've never seen a problem in binding repeaters to Hibernate-managed collections: because I never do it.
Ugo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
