> So what you are suggesting is another lifecycle method. I wonder if
> DataObjectTransactionEventListener would work in this situation?
This could work, but it seems to me that it takes the decision making
power away from the object. Normally, that's a good thing, but I think
in this case, isn't it best to let the object decide whether its
transient properties warrant "computing" persistent fields?
Maybe it can still work. I'll tinker with it a bit..
> I had issues with DataObject events design in the past, I guess
> mainly because a lifecycle interface was named a listener... But the
> functionality is there and will be preserved in some form even if we
> refactor the event.
>
> Andrus
>
>
This archive was generated by hypermail 2.0.0 : Wed Sep 28 2005 - 13:16:32 EDT