avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject RE: [phoenix] JMX Management - the good, the bad and the ugly
Date Thu, 26 Apr 2001 00:25:35 GMT
At 09:17  25/4/01 +0200, Leo Simons wrote:
>> >> DynamicMbeanFactory will throw exceptions when there is
>> get/is/set methods
>> >> that don't conform to JavaBeans standard where I think it should just
>> >> ignore them (Leo can you confirm that???).
>> >
>> >No (sorry). According to the specification, an object that us not a valid
>> >JavaBeam/MBean will not be exposed.  have no problem with going against
>> >that spec...it'd mean we could never claim actual JMX compliance though.
>> We are compliant with JavaBeans (they say ignore anything that doesn't fit
>> pattern)
>> however your implementation assumes that if they start with get
>> they MUST bet a getter (which is not true in our case). Same with
>> is and set.
>I fixed that, didn't I?
>whoops...old copy in the CVS...ouch.

>addendum: that might be tomorrow...actually thought it was the day
>after tomorrow today, so that my imaginary tomorrow would be the
>weekend. This is of course not the case as today is today and that
>other tomorrow is actually be a few days away which is why I did not
>say what I ment. (if you followed that on the first run, congrats.
>You're used to structural programming ;)

alternatively you used to be a logic student ;)



| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |

To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org

View raw message