struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject Re: Who's Handling BeanUtils and DynaBeans
Date Wed, 18 Dec 2002 01:50:41 GMT

On Tue, 17 Dec 2002, Doug Bateman wrote:

> Date: Tue, 17 Dec 2002 19:37:06 -0500 (EST)
> From: Doug Bateman <>
> Reply-To: Struts Developers List <>
> To:
> Subject: Who's Handling BeanUtils and DynaBeans
> Who's currently spearheading the continued development and
> maintenance of the Bean Utils and the new Dyna Beans?  I'd very
> much like to coordinate with you to see if I can help contribute
> to the continued development of this package.

It's being maintained as part of the Commons project -- development
oriented discussions occur on COMMONS-DEV (to subscribe, send an empty
other Struts folks, are involved over there too.

> A good while back, Craig had expressed interest in the design of
> a bean reflection library I had created prior to Struts.  At the
> time though, my work prevented me from contributing.  Things have
> changed now, and I'd like to help out in any way I can.
> Doug
> PS The sort of feature that attracted Craig's initial interest
> (this was a long while back) was the generality of the
> binding framework, which included interfaces like
> public interface IProperty
> {
>     public String getName();
>     public Object getValue();
>     public void setValue(Object value)
>         throws ReadOnlyException, ClassCastException;
>     public boolean isReadOnly();
>     public Class getType();
> }
> which allow you to find to an attribute, without being concerned
> whether it was in a JavaBean, Hashtable, DynaBean, RowSet, etc..

That's certainly one way to approach generic properties.  Something else
that's caught my interest in this regard more recently is that you can
craft an expression language interpreter that uses expressions like
"${}" which could work on beans, DynaBeans, result
sets, DOMs, ... also.

There's also a commons sandbox project called clazz with the goal of
building an abstraction layer API for things like this as well.


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

View raw message