We usually write a facade/adaptor class for complex Intake groups. There is something like an init() method which loads the constituent base objects, and the get/set methods simply pass the call on to the proper constituent.
It works well for us and simplifies the screen/action classes. Chris -----Original Message----- From: Marc Lustig [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 4:13 AM To: Turbine Users List Subject: AW: intake: mapping the group against 2 objects possible? > -----Ursprungliche Nachricht----- > Von: Scott Eade [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 18. Februar 2003 23:04 > An: turbine-user > Betreff: Re: intake: mapping the group against 2 objects possible? > > > On 19/02/2003 8:57 AM, "Marc Lustig" <[EMAIL PROTECTED]> wrote: > > > This is the standard code to populate the group with the data > from a bo, so > > that the form-data displays the existing values: > > > > #set($group=$intake.SomeGroup.mapTo($bo)) > > > > Q: is it possible to map the group against two different objects? > > > > What's the proper way to do that? > > Have you tried it? I suspect it will just work. It didn't really. I solved this by handling with two different groups, one for each of the BO's. This required to create another Intake group and setProperties() in the action for both groups. That's not a bad solution. --------------------------------------------------------------------- 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]
