The latest version of the JAXP Reference Implementation (RI), version 1.4, is currently available from the Java.net Maven repository. JAXP RI version 1.4 is part of J2SE 6.0 (a.k.a. "Mustang") and it is therefore available in the beta2 versions of the JDK and the JRE for J2SE 6.0.
Unless you have been living under a rock, you probably heard about the Java.net Maven Repository. This is a one-stop site where you can find artifacts for lots of Java.net projects.
The Japex jars are now part of the ever-growing Maven repository.
Since XML is a textual format, binary blobs must be represented as characters when embedded in an XML document. A popular encoding that permits this embedding is known as base64 encoding, and it corresponds to the XML Schema data type xsd:base64Binary.
Japex 1.0.9 now includes a new performance tracking tool. If you are a Japex user, or are planning on becoming one soon, you should check this out. The performance tracking tool can be used to send e-mail notifications for regressions (or progressions) based on a pre-defined threshold.
The Sun Java Streaming XML Parser (SJSXP) FCS version 1.0 is now available in binary and source forms from Java.net. This parser is an implemenation of JSR 173, submitted to the JCP by BEA.
Japex 1.0.3 is out with a number of very cool features. Since I didn't have a chance to blog about the features in version 1.0.2, I'll use this opportunity to talk about all the features that were added in the last few weeks.
So you just picked up the latest release of JAX-WS from Java.net and want to try it out with Glassfish. First, you need to override the version that is bundled with Glassfish, but how do you do that and be certain that you did correctly?
As more cores and harware threads are added to the new generation of micro-processors, the ability to easily test software scalability becomes increasingly important. Depending on the type and complexity of your application, using Japex may be a quick and simple way to verify the scalability of your code.
Paul Sandoz and I have developed an extension to Japex to support native drivers. This allows a benchmark to compare the relative performance of a C-based XML parser vs. a Java-based XML parser, for example.
Every native driver is an instance of the class com.sun.japex.jdsl.JapexNativeDriver which defines a native method corresponding to each phase in Japex.
Despite some similarities, performance testing and conformance testing are different types of activities, and certainly not every conformance test is necessarily a good performance test. There have been some attempts to using JUnit for performance testing, notably JUnitPerf.