On Fri, 04 Jul 2008, Matthijs Wensveen wrote: > How do you cope with deeply nested model properties? For example: > > public class PersonViewer extends Component<Person> { > .. > } > > some other component does: > person.getOrders().get(0).setAmount(0); // first order for free (as in beer)
I have no idea of Johan's project, but normally you just edit an object in one place at a time, and PersonViewer would be a read-only component with a model that always pulls the freshest version of the person it is displaying from the database. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]