On Sunday 15 February 2004 00:14, 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, is that not what you prefer?
or would you rather have that I wait until the merger has finished?
>
> > The patch removes the need to handcode the .mxinfo files by using the
>
> Phoenix
>
> > supplied doclet
> >
> > However for this to work we need to commit four additional .jar files
>
> (Steve
>
> > places them in tools/lib which makes sense)
>
> 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:
/**
* An interface to expose James management functionality through JMX.
*
* @phoenix:mx-topic name="DNSServer"
*/
public interface DNSServerMBean {
...
Then the .mxinfo files are autogenerated during the build process and put in
the james.jar.
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.
--Søren
> --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
