commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <>
Subject Re: [beanutils] 1.7.0 Release and LazyDynaBeans
Date Mon, 19 Jul 2004 13:08:26 GMT
Great thanks.

I did have a look at the beanification interfaces (were talking about
BeanUtils, PropertyUtils and ConvertUtils right?), but I'm not sure if I'm
on the same wavelength or not about the issues here. BeanUtils came out of
Struts originally and I like others in the early days hit the problem that
since they were all static methods the behaviour of BeanUtils couldn't be
overriden - you either had to customize Struts (not always allowed), live
with it or find another way. Whats been done in beanification clearly
resolves that issue but I guess now its a question how do we structure
things so various different behaviours can be easily plugged in.

Seems to me that most people are happy with accessing e.g. BeanUtils (rather
and BeanUtilsBean) through the static methods and that these should remain
as the BeanUtils interface. Whether things like BeanUtilsBean,
PropertyUtilsBean, ConvertUtils bean continue to mirror their static
interfaces or not in the future seems less important as they could probably
be re-organised with little impact on most peoples existing code. And where
people have adapted things like BeanUtilsBean for their custom behaviours -
modifying it for a new version of beanutils shouldn't be a big deal and
hopefully would be easier.

Don't know if this made any sense but my opinion is go ahead and release.


----- Original Message ----- 
From: "robert burrell donkin" <>
To: "Jakarta Commons Developers List" <>
Sent: Sunday, July 18, 2004 2:35 PM
Subject: Re: [beanutils] 1.7.0 Release and LazyDynaBeans

> On 16 Jul 2004, at 13:59, Niall Pemberton wrote:
> > Robert,
> Niall
> > Would it be possible to include the new "Lazy" DynaBean classes (i.e.
> > LazyDynaBean, LazyDynaMap and LazyDynaClass) in the 1.7.0 release? I
> > realise
> > its a maintenance release, but since these are new classes they have no
> > effect on backwards compatibility. I'm hoping that Struts will accept
> > some
> > changes which use these classes - but they need to be in a "released"
> > version of beanutils before I could put anything into Struts that
> > depends on
> > them. Also if there were any compatibility issues with the following
> > 1.7.1
> > release then Struts users could take advantage of these classes without
> > having any possible upgrade issues.
> i'll add them into the release branch.
> > Also, whats left to do for the 1.7.0 release - which (if any) of the
> > outstanding bugs are preventing the 1.7.0 release from going ahead?
> 1.7.0 is a service release rather than a bug fix one. the work on HEAD
> is aimed at 1.7.1 (which will be a bug fix release).
> the major hold up for 1.7.0 is that the beanification interfaces need
> reviewing (before they are fixed by the release). i've been hoping that
> i'd get some feedback from people but i now plan to go ahead with the
> changes today.
> - robert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message