Comments on: On the Violation of Java Access Control http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/ Technology and Geek Stuff by Eric Burke Thu, 04 Nov 2010 22:37:00 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: It’s Just a Bunch of Stuff That Happens » Blog Archive » You CAN Change Final Fields http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/comment-page-1/#comment-303 It’s Just a Bunch of Stuff That Happens » Blog Archive » You CAN Change Final Fields Sun, 14 Oct 2007 01:13:40 +0000 http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/#comment-303 [...] On the Violation of Java Access Control Oct [...] [...] On the Violation of Java Access Control Oct [...]

]]> By: Tim Vernum http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/comment-page-1/#comment-298 Tim Vernum Sat, 13 Oct 2007 14:14:05 +0000 http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/#comment-298 I think you're actually falling into an optimisation trap, not an access control trap. Try calling: System.out.println("Age field is " + ageField.get(caveman)); And you should find it is 100. The reason your code prints 10 is most likely due to the compiler optimising the implementation of getAge(). Because age is final, and has a single fixed value (10), it is possible for the compiler to optimise the implementation of "getAge()" to "return 10;" I think you’re actually falling into an optimisation trap, not an access control trap.
Try calling:
System.out.println(”Age field is ” + ageField.get(caveman));
And you should find it is 100.

The reason your code prints 10 is most likely due to the compiler optimising the implementation of getAge(). Because age is final, and has a single fixed value (10), it is possible for the compiler to optimise the implementation of “getAge()” to “return 10;”

]]> By: Alex Miler http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/comment-page-1/#comment-291 Alex Miler Fri, 12 Oct 2007 14:25:10 +0000 http://stuffthathappens.com/blog/2007/10/11/on-the-violation-of-java-access-control/#comment-291 Or of course, you can just modify the byte code when the class is loaded so the field is no longer final.... :) Trivial to do with ASM. Or of course, you can just modify the byte code when the class is loaded so the field is no longer final…. :) Trivial to do with ASM.

]]>