RE: Remaining tasklist for alpha?
"Bordet, Simone" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, > Hi all, > > What still needs done for alpha? Actually I am pretty confident about the implementation, so I would go to a beta directly. Ward is working hard on JMX 1.2 (thanks man !), and JSR 160 is still in EA2 compliance: we're waiting for JSR 160 final release and then we have to upgrade the implementation. Then we need examples and documentation. Another point that is not clear to me is the status of the HTTP adaptor: Carlos ? I was also thinking of moving the HTTP adaptor from mx4j.adaptor.http.* to mx4j.tools.adaptor.http.*. It is a breaking change, but I think the next release of MX4J will be named 2.0, so it is a major change and if we want to make this change better we do it now. I have in my sleeve 2 stuff: 1. A heartbeat implementation, a general one and for RMI (to notify the client when the server is down). 2. A configuration file implementation, which I'm using with great satisfaction (I posted about it some day ago). Anyone interested in these to be part of the release ? Simon ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54