This is it exactly... your example for Customer -> shippingAddress is exactly what I'm after... our customer records can have many addresses and was trying to figure out a good way to seperate this out.
It will take me a day or so to wrap my head around this methodology but I'm sure it will be worth it. I would be willing to write up a some documentation of my experience combined with the facade technique to add to the turbine docs when I'm finished. Thanks Jeff Painter [EMAIL PROTECTED] On Fri, 21 Mar 2003, Chris K Chew wrote: > Hi Jeff. > > It sounds like Intake will work well for the situation. > > One trick that we use often is to create a complex Facade class to which > intake maps. You can store the facade object in user.setTemp() through a > wizard, or have a big form that maps to the Facade, which maps to your > target objects. Search turbine-user for the thread "intake: mapping the > group against 2 objects possible?" on 02/19/2003 for a bigger explanation. > > Good luck, > > Chris > > > --------------------------------------------------------------------- > 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]
