Here is the text of the message I recently sent to the JSR 255
Expert Group, in my capacity as Specification Lead.
Eamonn McManus
I've mentioned in the past that one of the new features in
version 2.0 of the JMX API is "client contexts", which will allow
a client to communicate context information to a server, and a
server to adjust its behaviour accordingly. The most obvious
example is locale, where for example the client says that it is in
the French locale and the server translates its messages and
descriptions into French. How does this work? Read on. ...
The MXBean framework gives you a way to define MBeans with custom
types, and map those types to standard ("open") types so generic
clients can deal with them. Sometimes you want to do this mapping
outside an MBean. For example, we recommend that the custom
payload of a Notification should use open types, but open values
can be a bit painful to construct. It would be nice to use the
MXBean framework to map from a custom payload type to an open
type. Is there a way to do that? ...
You can't construct a JMX ObjectName without handling
MalformedObjectNameException, which is a checked exception. Here's
why that is a pain, how to relieve that pain, and what we're doing
to make it less painful in the next version. ...
The JMX Namespace feature has now been integrated into the JDK 7 platform. You can read about it in detail in the online documentation for javax.management.namespace. Here's my quick summary. ...
Shanliang Jiang talks about one of the main use cases of the Event Service from the new JMX API in this blog entry. You can use a wildcard ObjectName to subscribe to a set of MBeans. The Event Service tracks the arrival and departure of MBeans, so it will subscribe to new MBeans matching the pattern as they appear. The Event Service is already present in the latest draft of the JDK 7 API and you can try it out by downloading the latest snapshot.
Yesterday I cleaned up the "umbrella bug" that lists the
various things we are planning for version 2.0 of the JMX API,
which is the version that should be included in Java SE 7.
Here's a list of the things we were thinking of doing but are
not now planning to.
The new Event Service that is part of version 2.0 of the JMX API is available in the latest snapshot of the JDK 7 platform. ...
Version 2.0 of the JMX API is being defined by JSR 255. I've
written about some of the features in the new API before. They
are trickling into the JDK 7 sources over time, so you can now
play with some shiny new things. Here's a description of what they
are, and how you can even access them from JDK 6 if you are
brave...
This is the fifth and last installment in my summary of the sessions I
attended at JavaOne this year. This one covers everything that didn't fit into my neat categories. Capsule summary: Garbage First; JFugue; Semantic Web; VisualVM; Real-Time Java; Smartpens.
This is the fourth installment in my summary of the sessions I
attended at JavaOne this year. This one covers all the JMX sessions. Capsule summary: my presentation with Jeff; JMX security; JMX configuration in clusters...
This is the third installment in my summary of the sessions I
attended at JavaOne this year. This one covers concurrency. Capsule summary: Fork/join; data races; transactional memory...
This is the second installment in my summary of the sessions I
attended at JavaOne this year. This one covers Java programming practice. Capsule summary: Effective Java, second edition; FindBugs.
I was at JavaOne again this year, and this time I found time to
go to a surprising number of talks. I started writing a summary
of them but it grew to about six screenfuls, so I decided to
post it in installments. Here's the first installment, covering
the talks about Java futures...
