RE: [Openjmx-devel] [Fwd: Source code generation of MBean interfaces and descriptions]

[Bordet, S. <Sim...@co...>]

Hi,

> >No, see above... "if the attribute is write-only, then the=20
> setter will have the description."
> >It's in the openjmx implementation that I will do the trick:=20
> if getter present take its description and ignore the=20
> setter's, if no getter take the setter's one. However the=20
> trick costs nothing and it's completely transparent.
> >
> Ok. This will make it easier for me. Thanks :-)

It's not done however. Do you need it asap ?

> I will have to make a custom handler for the warning (whether=20
> or not we=20
> are trying to tell it's an operation when it's an attribute).

Well, if it's too complicated, you know, keep it simple for now.

> Anyway I have to because of the difficulty with indexes taken as=20
> parameters on the methods. There is no way using regulars=20
> XDoclet tags=20
> to solve this problem. Would I be allowed to extend the=20
> MBeanDescriptionAdaptor in order to take as input the name of the=20
> parameter? or do I have to solve this issue at source code=20
> generation time?

Not sure I understand, but for the last question, no.

The MBeanServer is calling the description implementation, and I don't =
know the *names* of the parameters of operations or constructors, and I =
cannot know them. So I cannot pass them to the description =
implementation.

Hope helped

Simon