commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@blueyonder.co.uk>
Subject Re: [beanutils] LazyDynaClass and LazyDynaBean Bug [29879]
Date Mon, 05 Jul 2004 00:37:17 GMT
Robert,

Thanks for replying and for the pointer to the wiki on etiquette.

I'll add myself to the project and I understand the point you make about
taking care over changing existing beanutils code - I'm primarily a Struts
user but with its dependancy on beanutils I realize the possible
consequences.

The "Lazy" bean patches are two new dyna bean classes and involve no changes
to existing code - plus there are two new junit test cases to test these
classes.

If I add these new classes in and someone comes back later and objects, they
can always be removed if the objections can't be resolved.

Niall

----- Original Message ----- 
From: "robert burrell donkin" <robertburrelldonkin@blueyonder.co.uk>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Sunday, July 04, 2004 11:28 PM
Subject: Re: [beanutils] LazyDynaClass and LazyDynaBean Bug [29879]


> 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
> (http://wiki.apache.org/jakarta-commons/JakartaCommonsEtiquette) 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.
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=29879
> >
> > 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: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message