I attached a test case patch to the bug report (My first JUnit - so go easy on me) The test case only deals with situations where a security manager is not present. I will have to add a security manager test case later. I'm not opposed to making the function public, in fact, after writing the test, I think that might be the way to go. I just think that if it is made public, code should be added to verify that the caller should be able to access a non-visible field. I don't like the way that the code fix I added causes a superfluous call to the security manager: m.setAccessable(). I want to correct that. I will also look at the private constructor issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050365#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...