Search |
||
Pinch MePosted by editor on June 20, 2008 at 7:40 AM PDT
A fully FOSS Java passes the JCK A day that the Java community has been working towards for a long time has finally arrived. It was one thing to say Java would be open sourced. It was another to annouce that it has been. But now, it can be proved: IcedTea's version of OpenJDK 6, with encumbrances removed, passes the Java Compatibility Kit. Rich Sharples has announced the accomplishment IcedTea, RedHat's effort to replace OpenJDK encumbrances with code from GNU Classpath, among other sources. "This week the IcedTea Project reached an important milestone - The latest OpenJDK binary included in Fedora 9 (x86 and x86_64) passes the rigorous Java Test Compatibility Kit (TCK). This means that it provides all the required Java APIs and behaves like any other Java SE 6 implementation - in keeping with the portability goal of the Java platform. As of writing, Fedora 9 is the only operating system to include a free and open Java SE 6 implementation that has passed the Java TCK. All of the code that makes this possible has been made available to the IcedTea project so everyone can benefit from the work." Congratulations are being posted in response to the announcement. Dalibor Topic writes, "congrats to Lillian and the team behind OpenJDK in Fedora on making it through the finishing line in time for FUDCon, and getting OpenJDK6 to pass the compatibility checks on x86-fedora9 and x86_64-fedora9!" David Herron's Great milestone reached by OpenJDK on Fedora looks at the history of the history of the effort to make Java fully FOSS compatible, and addresses misstatements and distortions from a related Slashdot thread. But we're not done, so let's give Dalibor the last word, the closing line from his latest blog: "On to the next distribution!" Also in Java Today, in an article for InfoQ, Jeroen Borgers asks the surprising question Do Java 6 threading optimizations actually work? "Much attention has been given by Sun, IBM, BEA and others to optimize lock management and synchronization in their respective Java 6 virtual machine offerings. Features like biased locking, lock coarsening, lock elision by escape analysis and adaptive spin locking are all designed to increase concurrency by allowing more effective sharing amongst application threads. As sophisticated and interesting as each of these features are, the question is; will they actually make good on these promises? In this two part article I will explore these features and attempt to answer the performance question with the aid of a single threaded benchmark." The latest JavaOne Community Corner Podcast is j1-2k8-mtT14: Java User Groups International Map, in which Van Riper describes how the JUG Map was created. He also demonstrates how individual JUGs can customize the JUGs Map to embed it in their own JUG pages like one that was set up for Silicon Valley JUGs. In today's Weblogs, John Catherino returns to his take on messaging APIs in Messaging vs. RPC? Let's fuse 'em. "The spirited debate following my last post on messaging being degenerate RPC got me thinking; is there some way to combine these two somewhat orthogonal methodologies, to create a unique hybrid approach? A bit of insight led me back to update the original cajo Queue messaging class, and the results were indeed most satisfying." Blame Sun for that? Fabrizio Giudici warns, "this is an entirely untechnical entry. Read only if you'd like to waste five minutes (was: Sun should invest more in ... advertising and public relationship)." Finally, Arun Gupta presents the Top 10 features of Hudson. "Kohsuke (aka Mr. Hudson) and I attended The Server Side Java Symposium, Las Vegas in Mar 2008. In one of the evenings we spent togehter, I decided to pick Kohsuke's brain on top 10 features of Hudson. My notes were lost but luckily I found..." The latest java.net Poll asks "Has the Java 6 Update 10 plug-in stoked your interest in applets?" Cast your vote on the front page, then visit the results page for current tallies and discussion.
In today's Forums,
Martin Grebac spot-checks a disabled WSIT feature in Re: WSIT usability - Re: [Issue 136408] Cannot enable TX support from the Edit web service Attributes dialog in an EJB project. "I got a request from tx guys to disable the field way back, and I don't remember the exact reasoning, so if anyone recalls please speak up, otherwise I'm fine with enabling the field in 6.5 builds. Just note that not specifying a tx annotation on an ejb method has a different meaning than not specifying a wsit policy assertion, because even with no access to QoS dialog or without any annotations specified, you already end up with tx policy assertions in the final wsdl."
Finally, Current and upcoming Java Events :
Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site. Archives and Subscriptions: This blog is delivered weekdays as the Java Today RSS feed. Also, once this page is no longer featured as the front page of java.net it will be archived along with other past issues in the java.net Archive. A fully FOSS Java passes the JCK »
Comments
Comments are listed in date ascending order (oldest first)
|
||
|