OnJava.com – reviewing the top 10 Java Request for Enhancements

Chris Adamson has an interesting article on the OnJava.com site reviewing the top 10 Request for Enhancements (RFEs) for changes and new additions to Java, in this case for the Dolphin release which is Java SE 7.0 (6.0 (Mustang) is already available for beta download – see download section here).

Some of the interesting requests are the addition of Design by Contract support using pre and post conditions, the addition of ‘struct’ support, and upgrading JEditorPane to support HTML 4.x (a jump from the current 3.2 support).

AMD confirm deal to buy ATI

This is big news. ATI have confirmed their deal to buy out ATI.

AMD have recently been giving Intel a run for their money with their superior AMD Athlon 64 and X2 dual core processors, which they were first to bring to the market long before Intel arrived with their Dual Core processors.

So what will this buy out mean for AMD and ATI? Will this put AMD in a much stronger position for taking on Intel now that it is coupled with one of the major graphics GPU producers? And how will this merger benefit ATI against it’s main competitor nVidia? It would seem that both companies would be able to leverage technologies from each other that would be benefical, but I wonder if this may be leading to the eventual release of a CPU with enhanced graphics capabilities, or a leap forward in graphics card performance with the addition of AMD co-processors on board, or something similar?

Taking control of your XML Parsing with StAX

The two most common XML parsing approaches both have their limitations. The DOM approach loads the whole XML doc into memory in it’s tree representation, which is great if you need to walk through the tree to process it’s content, but is inefficient if the XML is large or you are only looking for a small part of the XML. The SAX approach allows you to inspect the XML ‘on the fly’ and get notified of events (matching parts of the XML you are looking for). This avoids having to load it all into memory as in the DOM approach, but is a psuh-based approach which means once the parsing starts the XML streams through until the end of the document, and you have no control over navigating forward and backward through the stream.

java.net have a good introductory article today showing how the StAX API is used, which offers a pull-based approach. It avoids the limitations of DOM and SAX by allowing you to control the processing of the stream, and even terminate processing halfway though if you have found the data you are looking for, meaning you are not forced to wait until the end of the stream.