commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: [clazz] Scope?
Date Sun, 27 Oct 2002 16:56:23 GMT
Stephen Colebourne wrote:
> Scope, hmm, yes its a little tricky to define, which has been a concern of
> mine too.
> Use case 1:
> Provide standardised access to Beans - a replacement to Introspector.
> This covers simple, array, List and Map properties.
> It also covers non-standard naming conventions, eg. other than 'get' and
> 'set'.
> Use case 2:
> Property may not be a simple method call on the object.
> This enables a Map of data on the Bean to be treated as real properties.
> Use case 3:
> Handle non-standard Bean types.
> This covers the ground that DynaBean covers. Beans that aren't written as a
> new class, but instantiated instead as instances of the same class.
> Use case 4:
> To be able to store attributes (meta-data) against classes.
> Initially conceived as just a store used at runtime, has developed into the
> ability to pickup values from XML files, and generated source/byte code.
> #1, #2 and #3 are the key ones for tools such as Betwixt, Jexl, JXPath and
> so on to be able to locate what properties there are on an object in a
> pluggable way.
> #4 just seems to drop out as an additional benefit. It wasn't my immediate
> goal.
> There is possibly a question of whether there is one or two projects here. I
> would like to keep it as one for the moment. If the metadata stuff becomes a
> big thing then the bean stuff breaks out at that point.

Ok.  I *really* want #4.  All the rest of the stuff is nice, but not necessary
for my purposes.


"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin

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

View raw message