Hi, another problem I've detected is that the spec defines |> "mon.statusvariable.value: The value of the StatusVariable, represented as a String"
but the implementation currently delivers events containing values of type Integer,Float,Boolean or String. Regards, Martin Martin Thelian schrieb: > how should I report problems I've detected while testing the MA > implementation? > I'm also willing to provide patches to get it to run properly. > > Problems I've detected so far: > - IllegalArgumentException in monitor-job if an monitorable is > unregistered while there is a job monitoring it > - NullpointerException in unsubscribeStatusVariables while calling > stop on a scheduled job > - returning null in monitorable-getStatusVariable causes the whole > monitor-job to terminate > > Regards, > Martin > > Didier Donsez schrieb: >> Martin >> [1] is mainly a quick implementation of the Monitor Admin spec >> in order to understand the principles of this specification. >> It is not robust and its TODOLIST is long (permission check, >> synchronization, ...). >> I don't know if MA is implemented by other FOSS OSGi communities. >> >> Those following bundles can be used to play with the MA >> http://svn.apache.org/repos/asf/felix/sandbox/donsez/monitor.jobcmd/ >> http://svn.apache.org/repos/asf/felix/sandbox/donsez/monitor.sample.memorymonitor/ >> >> http://svn.apache.org/repos/asf/felix/sandbox/donsez/monitor.sample.memorymonitorjob/ >> >> http://svn.apache.org/repos/asf/felix/sandbox/donsez/monitor.sample.usagemonitor/ >> >> >> Somebody may complete this implementation. >> >> Kind regards, >> >> Didier >
