"alesj" wrote : "adrian(a)jboss.org" wrote : In case its not clear
| Nope, not clear. :-)
| OK, I'm glad I didn't introduce security hole :-), but I don't see why
your example will fail with the current code?
|
It won't fail with the current code.
anonymous wrote :
| And you're saying this field.setAcceessible should be in privileged block?
Yes, this object gets cached and used across threads. You can't guarantee
that the caller will be able to setAccessible(), but they still want to be able
to use the FieldInfo (even if they can't invoke on it).
Write some tests for the security stuff then you'll understand.
e.g. A caller doesn't have permission to setAccessible()
but still wants to generate a BeanInfo for the class (without the private fields).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137053#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...