Both the hibernate collection and Cforms repeater handle add/change/delete logic. If you introduce an intermediate collection, don't you have to re-implement that logic in order to create an effective mapping from one to the other? For example, if I delete a row from the Cforms repeater, how do I make thje corresponding change to the hibernate collection?
Joel McConaughy Managing Partner Displayware LLC 800 Fifth Ave., #101-316 Seattle, WA 98104-3191 206-300-4732 Direct 206-382-2188 Fax [EMAIL PROTECTED] -----Original Message----- From: Ugo Cei [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 28, 2004 9:46 AM To: [EMAIL PROTECTED] Subject: Re: Cocoon: Language Babel -or- Database Development Platform ? Il giorno 28/apr/04, alle 18:20, Joel McConaughy ha scritto: > IMHO, an out-of-the-box hibernate/cforms binding (or some other O/R > framework) should be a hard requirement -- otherwise where is the > productivity gain? Personally I'd feel a slight unease at the thought of directly bindiing a Hibernate-managed collection to a CForms repeater. I'd rather do it via an intermediate collection and hide the real data from the form, but that's just me. Ugo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
