DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7135>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7135 Misleading error message when beaninfo class conflict occurs [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2002-11-02 15:49 ------- this is probably overdue for a fix. i don't really want to add another exception the signature but it should be possible to create a subclass of one of the existing exceptions. this can then be caught by anyone who's bothered. probably a subclasses of java.lang.IllegalArgument since that's what's being thrown at the moment. in the medium term, it should be possible (but is it wise?) to create a workaround for this problem. we could check that the BeanInfo is about a class that is assign-compatible. if not, we perform the require introspection ourselves and return an BeanUtils instance created by ourselves. - robert -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
