commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: [beanutils] LazyDynaClass and LazyDynaBean Bug [29879]
Date Sun, 04 Jul 2004 22:28:53 GMT
hi Niall

(apologies for my tardiness in replying.)

infrastructure were fiddling around with nagoya a short while ago and i 
think some mail from bugzilla may have been lost for a while.

thanks for taking the trouble to write recommending the patches - they 
look promising. the main problem is that though beanutils is on my 
agenda (it's the next release i'm cutting after jaxme) there's a ton of 
work i need to do on the release branch.

there is a wiki page on etiquette 
( but 
(unless anyone else has an objection) i'd be happy for you to have 
beanutils karma. (just remember to add yourself to the status file 
before committing anything.) beanutils is very short staffed (so any 
help would be gratefully accepted) but is very widely used (so there 
are a number of things that need to be borne in mind when changing 
existing code). it's probably best to discuss changes before diving in.

- robert

On 2 Jul 2004, at 16:27, Niall Pemberton wrote:

> I created a bugzilla enhacement request (with code)  Bug [29879] to add
> LazyDynaBean and LazyDynaClass to beanutils - I don't know if the 
> problem is
> my end but I didn't see the usual emails arrive on this list so I 
> thought I
> would post this as well.
> I developed "Lazy" implementations of DynaBean and DynaClass and they 
> have
> been available for people to download from my web site for a while - 
> would
> there be any interest in having them in beanutils?
> LazyDynaClass is an implementation of the MutableDynaClass interface 
> that
> allows the properties of a DynaClass to be changed.
> LazyDynaBean must be used in conjunction with a MutableDynaClass and
> automatically adds properties when its set() methods are called if the
> property doesn't exist. The versions available on my web site only 
> dealt
> with "simple" properties, but I now have a version that caters for 
> indexed
> and mapped properties as well.
> This version automatically instantiates a Map when a mapped property 
> is set
> that doesn't exist.
> It also instantiates either a List or Array when an indexed property 
> is set
> that doesn't exist and automatically "grows" the List or Array so that 
> it is
> big enough to cater for the index being set.
> Quite a few people seem to be using them now and I've had good 
> feedback.
> I'm not sure of the Commons "etiquette" here - I was recently voted a
> Commons committer for the Validation project - but I guess I don't have
> karma for beanutils and even if I have, houldn't just plough in adding 
> stuff
> without the existing Beanutils commiters say so?
> Niall
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message