at the moment, the answer is: not easily. the problem is that beanutils is rather hamstrung by backwards compatibility. there has been talk of factoring out the exception handling so that it could either be hooked into by a pluggable interface or the behaviour subclassed.

or maybe there's a case for developing subclass exceptions.

anyone else have any opinions on this?

- robert

On Friday, August 15, 2003, at 07:10 PM, K.C. Baltz wrote:

Is there any way to get BeanUtils.copyProperties to let you know which property failed when you get an "argument type mismatch"? Right now, I just get an exception and am left to guess which bean property didn't match.

K.C.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to