> Noel J. Bergman wrote: > > > I am just getting ready to commit Steve Shorts JMX extensions. > > To where? MAIN?
> Well both MAIN and branch_2_1_fcs Ah, that's cool. :-) > > > The patch removes the need to handcode the .mxinfo files by using the > > > Phoenix supplied doclet > > Is this a build time process? I am possibly OK with the doclet approach > > (can you provide an example?) if it is strictly a build time issue. > It is strictly a build-time issue. You place tag in the MBean interface > like this for the DNSServerMBean: > * @phoenix:mx-topic name="DNSServer" > The same thing is possible for .xinfo files and it is documented (rather > well actually) at the phoenix site. > I thought that this was not used because we for some reason did not want > to introduce more tools or something. I don't know of any reason not to use a tool, but we should make sure of Avalon's plans. Hopefully they are maintaining compatibility as they add JMX into Merlin. I looked at http://avalon.apache.org/merlin, the Avalon Wiki, and the mailing lists, but couldn't find anything other than some e-mails back in September, so I am cc'ing Stephen to make sure we get a response. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
