SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
JDBCSupport - An easy to use, light-weight JDBC framework -
nitin pokhriyal wrote:fred
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
nitin pokhriyal wrote:Thanks to three of you.
I think ernest and fred were right about security manager but Sebastian i asked about only accessing private method security not about securing my class. so your solution doesn't seems to be working in this case. correct me if i am wrong
JDBCSupport - An easy to use, light-weight JDBC framework -
Sebastian Janisch wrote:
nitin pokhriyal wrote:Thanks to three of you.
I think ernest and fred were right about security manager but Sebastian i asked about only accessing private method security not about securing my class. so your solution doesn't seems to be working in this case. correct me if i am wrong
Yes if it's not the Constructor you want to protect then your best bet is the security Manager
R van Vliet wrote:
It is a little odd. By default you cannot actually invoke private methods using the default security manager. But then it does allow :
After which you can invoke the private method. Bit silly.
Henry Wong wrote:
R van Vliet wrote:
It is a little odd. By default you cannot actually invoke private methods using the default security manager. But then it does allow :
After which you can invoke the private method. Bit silly.
That's how (or more correctly, when) the security manager is called. The setAccessible() method is the method that invokes the check with the security manager.
Henry
Consider Paul's rocket mass heater. |