I need to use the 2.0+ series of code unless 3.0 will be ready for primetime in the next 2 months.
Thanks -- Garry Watkins Database Administrator Motley Rice LLC 843-216-9639 > From: Andrus Adamchik <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > Date: Mon, 30 Oct 2006 17:08:12 -0500 > To: <[email protected]> > Subject: Re: Is there an awakeFromInsertion equivalent in cayenne? > >> but I believe Andrus mentioned >> there'd be other ways of doing it in 3.0 > > Yes - and this seems to be the killer feature in 3.0 - it's been > discussed like a dozen times in the past month. Here is a few links: > > http://cwiki.apache.org/CAYDOC/lifecycle-callbacks.html > http://objectstyle.org/cayenne/lists/cayenne-devel/2006/10/0112.html > > Andrus > > > On Oct 30, 2006, at 3:35 PM, Michael Gentry wrote: > >> setPersistenceState is what I use, too, but I believe Andrus mentioned >> there'd be other ways of doing it in 3.0 and I believe there were some >> ROP issues with it, too. If you aren't using ROP, you should be fine. >> >> /dev/mrg >> >> >> On 10/30/06, Bryan Lewis <[EMAIL PROTECTED]> wrote: >>> Not directly. When we converted our old WebObjects apps, we made a >>> custom superclass that hooks setPersistenceState(): >>> >>> /** >>> * When any of our objects is inserted, call a method >>> * awakeFromInsertion() to allow the object class to do >>> initialization. >>> */ >>> public void setPersistenceState(int state) >>> { >>> super.setPersistenceState(state); >>> >>> if (state == PersistenceState.NEW) { >>> awakeFromInsertion(); >>> } >>> } >>> >>> /** >>> * The default behavior for awakeFromInsertion() is to do >>> nothing. >>> */ >>> public void awakeFromInsertion() >>> { >>> } >>> >>> >>> >>> >>> >>> Watkins, Garry wrote: >>>> I need to set up some default values. Is there an equivalent to >>>> awakeFromInsertion (WebObjects) for Cayenne? >>>> >>>> Thanks >>>> >>> >>> >> > Confidential & Privileged Unless otherwise indicated or obvious from its nature, the information contained in this communication is attorney-client privileged and confidential information/work product. This communication is intended for the use of the individual or entity named above. If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and destroy any copies--electronic, paper or otherwise--which you may have of this communication.
