|
From: Bordet, S. <Sim...@co...> - 2002-01-18 16:32:11
|
Hi Jerome,
> >Ok, I thought some more on it, what about this ?
> >
> >/**
> > * @openjmx:managed-attribute description=3D"The status of this =
MBean"
> > */
> >public int getStatus() {return 0;}
> >/**
> > * @openjmx:managed-attribute
> > */
> >public void setStatus(int status) {}
> >
> >I specify always on getter the description information; I=20
> just put the tag on the setter so that it will appear in the=20
> MBean interface. I will do a small change to the code so that=20
> getters are always processed before setters, so setters can=20
> have no description; if the attribute is write-only, then the=20
> setter will have the description.
> >
> >About access I don't care anymore.
> >
> I have attached another proposition I have. There is the=20
> implementation=20
> (a little bit more complex than before) and the resulting=20
> interface and=20
> description.
> I am now trying to verify if there are the getter/setter methods.
-1 :)
Because you have to specify at class level the attribute name, which in =
case of renaming is a pain...
I still prefer my solution.
> Where do you want to emit the warning? in the resulting=20
> description? or=20
> on screen during the build process?
> The first option is easier and the later is more complex.
The later will be perfect ;)=20
Simon
|