On Mon, 16 Apr 2001, Geir Magnusson Jr. wrote:

> "Craig R. McClanahan" wrote:
> > 
> > One nitpick along with my +1 -- the property setting stuff relies on the
> > code that is now in "beanutils" in Commons already.
> > 
> 
> Would it make any sense to move it into beanutils?
> 

You mean Digester itself?  I don't think so, if we are talking about
fine-grained components.  Consider:
* Beanutils is very narrowly focused on low-level introspection based
  functionality, and can be used underneath multiple higher level APIs.
* Struts uses beanutils separately from the indirect use via Digester
  already, to support the property-related custom tags it has.
* Anyone using ExtendedProperties (nee Configuration) for config files
  instead of XML-based files doesn't need the extra baggage of XML
  parsing in the beanutils component.
* Anyone not using XML at all would certainly *not* appreciate adding
  an XML parser dependency to use the basic beanutils stuff.

Craig

Reply via email to