https://issues.apache.org/bugzilla/show_bug.cgi?id=51730
--- Comment #2 from Irina Marudina <ir...@marudina.net> 2011-08-31 14:38:52 UTC --- It seems to be an issue in the java.beans.Introspector. I have produced a simple test program and reported the bug to Oracle: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7084904 Actually the reason to think it is a problem in Tomcat is because I tested with Apache Common BeanUtils and it worked fine. But it seems the reason is that they have applied a special workaround as explained here: --- Known Limitations Accessing Public Methods In A Default Access Superclass There is an issue when invoking public methods contained in a default access superclass. Reflection locates these methods fine and correctly assigns them as public. However, an IllegalAccessException is thrown if the method is invoked. MethodUtils contains a workaround for this situation. It will attempt to call setAccessible on this method. If this call succeeds, then the method can be invoked as normal. This call will only succeed when the application has sufficient security privilages. If this call fails then a warning will be logged and the method may fail. --- Source: http://commons.apache.org/beanutils/api/org/apache/commons/beanutils/MethodUtils.html -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
