Tom HawtinThomas Hawtin's WeblogAnother nail in the coffin of Thread.suspend.- February 21, 2006 Thread.suspend has been deprecated since 1.1, for good reason. "Thread.suspend is inherently deadlock-prone. If the target thread holds a lock on the monitor protecting a critical system resource when it is suspended, no thread can access this resource until the target thread is resumed. If the thread that would resume the target thread attempts to lock this monitor prior to calling resume, deadlock results. Such deadlocks typically manifest themselves as "frozen" processes." -- Why Are...http://www.jroller.com/tackline/entry/another_nail_in_the_coffin Reflection overreach- February 12, 2006 Two months ago I was on about how reflection in trusted code can cause security flaws. I stated, "A conservative policy is to only allow access to public items." That is not necessarily conservative enough. I noticed the other day that you should not be able to access sun. packages (and in WebStart com.sun.javaws., com.sun.deploy. and org.mozilla.jss.). If your code is trusted, then SecurityManager.checkPackageAccess appears to be the method you need to call to check whether a package is on the.http://www.jroller.com/tackline/entry/reflection_overreach Regressing mustangs- February 7, 2006 It appears that I have the first non-duplicate, non-Hello World(s)! entry to appear in the Project Mustang Regression Challenge. Okay, it's on the contrived side. Looking through the diffs I found something while still at java.a. A much more useful and easier approach is to run your own applications and test suites on it. If your app gets screwed up when Java SE 6 is launched, then it's your fault for not having the fix made. Of course, the exercise may also throw up bugs in your coding. On...http://www.jroller.com/tackline/entry/regressing_mustangs |