Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 15972 invoked from network); 31 May 2002 11:28:21 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 31 May 2002 11:28:21 -0000 Received: (qmail 5810 invoked by uid 97); 31 May 2002 11:28:12 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 5745 invoked by uid 97); 31 May 2002 11:28:11 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 5670 invoked by uid 98); 31 May 2002 11:28:10 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Re: Betwixt & MethodUpdaters From: Jason van Zyl To: Jakarta Commons Developers List In-Reply-To: <140101c20876$b5d54010$9865fea9@spiritsoft.com> References: <1022780237.14263.116.camel@localhost.localdomain> <140101c20876$b5d54010$9865fea9@spiritsoft.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 31 May 2002 07:28:02 -0400 Message-Id: <1022844482.3290.139.camel@localhost.localdomain> Mime-Version: 1.0 X-Authentication-Info: Submitted using SMTP AUTH PLAIN at fep04-mail.bloor.is.net.cable.rogers.com from [24.157.133.102] using ID at Fri, 31 May 2002 07:28:02 -0400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 2002-05-31 at 03:42, James Strachan wrote: > Hi Jason > > From: "Jason van Zyl" > > Hi James, > > > > Is is possible to control at which point updaters are called with newly > > created objects? > > > > In Maven the project object has a method: > > > > void addDistribution(Distribution distribution) > > { > > distributions.add(distribution); > > } > > > > But I would additionally like to place the distributions in a Map so > > that I can subsequently look them up but it appears that the > > distribution object added is not yet complete. > > > > This isn't a huge deal because I can lazily initialize the distribution > > Map I need but I was just wondering if the addXXX() method can be > > delayed until the object has been fully populated. > > It'd be a good idea to do this by default I think. > > Some hacking of the BeanCreateRule should do the trick; to move the call of > the updater from the begin() method, called on the start of the element to > the end() method after the bean has been completely initialized. We'd > probably have to introduce a stack to keep track of the beans; I think one > of the reasons I did it this way was I could avoid writing that bit of code > ;-) > > Wanna have a go or would you like me to do it? I can take a crack at it, I might take a look at some of the refactoring we were talking about too. But it's looking great and it's working in Maven very nicely. I'm glad to be rid of the xo mapper: that can now be culled and I'll work on betwixt/digester now. Thanks for getting it all up and running with the tests! > James > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: -- jvz. Jason van Zyl jvanzyl@apache.org http://tambora.zenplex.org -- To unsubscribe, e-mail: For additional commands, e-mail: