Hi Jared, You can call nullifyDates() in the configure method of your decorator. Transfer will fire the configure method before returning the new object.
Paul On Fri, Nov 28, 2008 at 1:28 PM, Jared <[EMAIL PROTECTED]> wrote: > > I read through this thread, but I still don't understand how to handle > the problem where date properties of a transfer object default to Now > (). I find that weird. Why don't they default to the null value for > dates? Setting them to Now() is a bit like defaulting string values > to "hello there" or defaulting numeric values to 17. I can't write a > configure method to handle this, since I don't want to always set the > date values to null (or whatever stands in for null, since CF doesn't > have null (which is annoying)). I only want to do so in response to > Transfer.new(). The only thing I can think of is to write a method in > my decorator called nullifyDates() that goes through each date and > does a setMyDatePropertyNull(). Then, whenever I do a new() for this > type of object I would, on the next line, do a myObj.nullifyDates() to > fix the weirdness of dates defaulting to Now(). Seems like a bit of a > hack. Is that the only way? > > That said, transfer is great! Long live transfer. Send Mark money. > > > > -- Paul Marcotte Fancy Bread - in the heart or in the head? http://www.fancybread.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" 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/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
