It looks like v1.32 of BeanUtils caused the problem.
Here's the (massive) setProperty method code I think (but haven't tested)
causes the issue:
} else if (ConvertUtils.lookup(value.getClass()) != null) {
newValue = ConvertUtils.convert(value.toString(), type);
} else {
The toString() call on value doesn't make any sense to me, as the
converter should be able to handle any object not just strings.
I'll make the change locally and retest/repost.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
