On Mon, 20 Aug 2001, Craig R. McClanahan wrote:
> Actually, you don't even need a new rule -- just a BeanInfo class for your
> bean that does the appropriate mapping. BeanUtils (which is used
> underneath) follows standard Java introspection mechanisms - it does not
> assume that the setter for method foo is always named setFoo().
Another partial workaround for JVZ's original problem, until the
underlying design issue in Digester is addressed, is to use
FactoryCreateRule instead of ObjectCreateRule to create the objects.
This lets you perform your own mapping of attribute names to property
setters using whatever approach is appropriate. (In Jason's test case
this would deal with the outer element, but not the inner one.)
Craig
