Blogging Techstacks

Apple Posts Java for OS X 2012-006 1.0 Update

Apple posted Java for OS X 2012-006 1.0 update today, which is available for OS X 10.7 and above. This update removes the Apple provided java plug-in from web browsers installed on your system, removes the Java Preferences application from the system, and brings the installed version of Java up to 1.6.0_37.

In addtion to this update, OS X 10.6 users can update to Java for Mac OS X 10.6 Update 11, which provides the same changes.

Java 1.6.0_37 is the Java 6 release containing fixes for some serious security vulnerabilities, including a well publicized one allowing an untrusted java applet to execute arbitrary code outside of the Java sandbox. More informatation on the Security Changes in the release can be found in the document: About the security content of Java for Mac OS X 10.6 Update 11 and Java for OS X 2012-006. The Java SE Development Kit 6, Update 37 Release Notes contain information on all that is new and changed in the Java 1.6 Update 37 release.

8 Ways to Improve Your Java EE Support Skills

Great post from Pierre-Hugues Charbonneau: 8 Ways to Improve Your Java EE Support Skills

My favorite (funny) quote from the article:

One of the great things about Java EE production support is the multiple learning opportunities you are exposed to.

One of the many important tips and points made in the article includes this one in regards to administrators general reluctance when making production changes:

Finally, if you feel that you are lacking technical knowledge to implement the changes, simply say it and ask for another more experienced team member to shadow your work.

Java EE Training Developer Considers Tomcat Use "Downright Harmful"

One of the popular posts on JavaBlogs over the weekend was an article titled "Goodbye Tomcat", posted on a blog run by a firm that provides Java Enterprise Edition mentoring and training. This excerpt from the first paragraph:

I am writing this article to point out how Java EE 6 changes things and why using tomcat could be downright harmful.

I'm hoping that the author will post something in an update to the article that will explain the harm that tomcat could be causing because it isn't there yet. I'm beginning to think the only harm tomcat may be causing is to J6EE adoption rates. ("Oh, snap!" - Editors)

I'm not trying to sound pro-Tomcat here, especially because I like JBoss and use it every day but there is a simple reason why Tomcat is so popular—that's all the app or website needed.