The Source for Java Technology Collaboration
User: Password:



Eamonn McManus's Blog

Eamonn McManus Eamonn McManus is the technical lead of the JMX team at Sun Microsystems. As such he heads the technical work on JSR 255 (JMX API 2.0) and JSR 262 (Web Services Connector for JMX Agents). In a previous life, he worked at the Open Software Foundation's Research Institute on the Mach microkernel and countless other things, including a TCP/IP stack written in Java. In an even previouser life, he worked on modem firmware in Z80 assembler. He is Irish, but lives and works in France and in French. His first name is pronounced Aymun (more or less) and is correctly written with an acute accent on the first letter, which however he long ago despaired of getting intact through computer systems.



JSR 255 (JMX API 2.0) is postponed

Posted by emcmanus on June 16, 2009 at 06:31 AM | Permalink | Comments (0)

Here is the text of the message I recently sent to the JSR 255 Expert Group, in my capacity as Specification Lead.

Dear experts,

I'm sure that you saw some months ago that our work on JSR 255 will not be part of the JDK 7 release (http://openjdk.java.net/projects/jdk7/features/). This decision was made here at Sun in order that some of the higher priority features could be properly resourced, in particular for the TCK work.

So, we need to retarget our work for JDK 8. This note is to give you an update on how I plan on handling that properly.

Over the next month or so, I'll be setting up a new OpenJDK project called "JMX2" where the Reference Implementation work for JSR 255 will live. This means that all our specification and RI work on JSR 255 will continue to be available to all to evaluate, critique and try out, and it will be up to date with the stable JDK milestone releases.

In order to do this, I will prepare a big changeset (call it the "undo changeset"), which will change the JMX API back to what it was in JDK 6, and apply that to JDK 7. Then, I will kick off the new workspace as a clone of the JDK 7 repository, including the undo changeset. I will immediately apply a "backout" changeset that undoes the undo (using Mercurial's backout command), so JMX2 is where JDK 7 was before I started.

I hope to have better news about making progress with the TCK as the JDK team starts planning JDK 8, which is likely to be towards the end of the JDK 7 cycle (http://openjdk.java.net/projects/jdk7/calendar/), at the beginning of next year.



June 2009
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        


Search this blog:
  

Categories
Community: Java Communications
Community: Java Enterprise
Community: Java Specification Requests
Community: Java Tools
Community: Java Web Services and XML
Community: JDK
Community: NetBeans
Distributed
J2SE
JavaOne
JSR
Open Source
Performance
Porting
Programming
Security
Tools
Web Services and XML
Archives

June 2009
December 2008
November 2008
October 2008
September 2008
August 2008
May 2008
April 2008
February 2008
December 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
July 2006
June 2006
May 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005

Recent Entries

JSR 255 (JMX API 2.0) is postponed

Client context in the new JMX API

Applying MXBean mappings to your own types



Powered by
Movable Type 3.01D


 Feed java.net RSS Feeds