Kirill Grouchnikov's Blog: Mustang synergy - the sum is less than the total of the parts?

My pages	Projects	Communities	java.net

Get Involved

java-net Project

Request a Project

Project Help Wanted Ads

Publicize your Project

Get Informed

java.net Online Books

java.net Archives

Get Connected

java.net Forums

Wiki and Javapedia

People, Partners, and Jobs

Java User Groups

RSS Feeds

Search

Online Books:

java.net on MarkMail:

Advanced Search

Kirill Grouchnikov's Blog

«Backstreet boyz "404 File not found" lyrics | Main | How single can your singleton instance be? »

Mustang synergy - the sum is less than the total of the parts?

Posted by kirillcool on August 22, 2005 at 11:41 PM | Comments (1)

The early access and weekly builds of JAXB 2.0 have been available for quite a few months now right here on java.net. A few weeks ago JAXB 2.0 made its way to Mustang weeklies.

As the minimal JRE requirement for JAXB 2.0 is Tiger (5.0), in case you wish to use it, you have to bundle JAXB 2.0 runtime binaries with your application (unless you are explicitly targeting Mustang). You would expect, of course, to run smoothly under Mustang with the same binaries (even if they provide the same classes). However, that is not the case with the latest build (48) of Mustang - a lot of class-related issues for both design-time (XJC) and runtime binaries of the latest JAXB 2.0 RI weekly. I wouldn't blog here on such a small issue, but it raises more interesting questions.

What is the magnitude and the complexity of taking weeklies from java.net CVS-based projects and putting them to Mustang? Can they be synchronized weekly, or Mustang weeklies are bound to lag behind? Are there some minimal acceptance tests done? How many such java.net projects are integrated weekly (besides JAXB 2.0 and JAX-WS 2.0)? What could be done to ensure that all parts play well when i take the "latest of everything"?

Eventually, i had to remove the Mustang b48 installation completely. Although in command-prompt and IDE i can choose the JRE myself, in Web Start i wasn't able to uncheck the "System" VM (6.0) and make 5.0 to be default. There went another free tester for Mustang - now I'll run all my development under Tiger :(

Bookmark blog post:

del.icio.us

Digg

DZone

Furl

Comments

Comments are listed in date ascending order (oldest first) | Post Comment

Hi Kirill,
Mustang weeklies do lag behind the java.net builds. We have milestone integration dates and we try to sync those up then. Since there are a lot of components being integrated on Mustang so it may not be possible to synchronize our java.net bits exactly with Mustang every week.

Besides there are other issues like version control, build processes, testing and other approvals which we need to obtain before api changes go in the JDK which is different from how we do stuff in the JAXB RI

Also there are going to be issues since the classes are a part of the JDK and if you use the latest bits from java.net, the ones from the jdk will take peference and this may cause different errors at compile time and runtime . You can use the endorsed standards / Xbootclasspath mechanisms to override the classes in Mustang with the latest implementations from java.net.

We would still appreciate your free testing and feedback :)either by using the classes in the JDK 6.0 or by using the latest and using the endorsed standards.

Gradually as implementations become final it will be bug fixes only in the jdk so we hope to do that on a more frequent basis but there could still be a lag.

I hope I could address your concerns.

Regards,

Bhakti Mehta

Posted by: bhaktimehta on August 23, 2005 at 05:33 PM

Powered by
Movable Type 3.01D

java.net RSS Feeds