Can you post some example code of your current thinking as a GitHub project and we can work on refining it and tuning Mapper/MetaMapper to suit your needs?
On Tue, Jan 5, 2010 at 7:47 AM, Jeppe Nejsum Madsen <[email protected]>wrote: > Hi, > > I'm trying to extend Mapper with a new MappedField type (basically > same as OneToMany, with date/time interval) > > So the mapped field in the owner object holds a collection of child > objects. When I save the owner, the childs should be > updated/inserted/deleted as well. > > The owner can contain several instances of the MappedField I would like > each of these fields to hook into the lifecycle of the owned object. > > I could use the LifecycleCallbacks trait, but this seems like > notification only. Ie if a save of the child fails, I don't see this in > the call to owner.save. > > I could create a trait to mixin to the MetaMapper which overrides save, > delete etc, but I would have to mix this in one time for each field the > way I see it.... > > Any hints? > > /Jeppe > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
