commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rune Johannesen <>
Subject RE: [BeanUtils] - Extensions for dotted queries...
Date Wed, 23 Apr 2003 18:51:45 GMT
Hi again, Robert!

Just a few comments from my side related to the issues you raised.

1) Naming convention

I called the class "Object"-Utils because it allows you to query "container"
like data structures (i.e. arrays, List objects, Map objects and
Collections) as result objects in addition to the standard bean properties.
Per definition Map, List and array objects are not a beans, thus "object".

I realise that the naming of the class is a bit unfortunate, especially
since the Commons-Lang has a class:	


Therefore we might consider renaming it (what about BeanObjectUtils?) or
perhaps include the features as dedicated methods in the existing BeanUtils
class. I don't have any strong opinions about how it is done - the easiest
way to contribute with the changes was to simply add new classes.

2) Scope

In my opinion this would be within the scope of the BeanUtils project since
the aim is to be able to continue querying the objects returned from bean
properties, even though the return objects themselves aren't (necessarily)
beans. The existing nested properties only allows you to continue the query
if the returning object is a bean. My intent was not primarily to add
support of non-beans, but to to extend the existing beans property querying
system to allow queries in arbitrary return objects in a consistent fashion.

3) Backwards compatibility

These changes should be bulletproof with respect to backwards compatibility.
None of the existing classes are changed, and as long as the class names and
method signatures of the existing classes aren't modified we should be fine.
Adding classes or distinct method signatures I don't regard problematic.

4) DynaBean support

As I am not experienced with the usage of the DynaXXX myself I would
appreciate if someone more familiar with that concept takes on the task to
support it. If that doesn't happen I am happy to do it.


Rune Toalango

PS! The conclusion after a discussion with P. Hammant was to withdraw the
NestedObjectUtils (too specialised behaviour/use case), but to submit the
ObjecUtils class

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

View raw message