Great, I look forward to seeing it in action. :-) What are you using for a client on the
other end of the SOAP connection?
I will go ahead and add helper methods to return any Instrumentable, Instrument, or
InstrumentSample given their fully qualified names. Should be fairly easy to do. Most
of the code is already there.
I'll post again when its done.
Cheers,
Leif
Marcus Crafter wrote:
Hi Leif & other Instrumenters!
Hope all is well!
I wanted to ask you a question about DefaultInstrumentManager
and the inclusion of a possible helper method to make accessing
samples easier.
I've managed to write a InstrumentManageable component which gets
a reference to the InstrumentManager in Cocoon. Using an Axis
AvalonProvider that I wrote I can now export instrumentable
samples via SOAP. Yippee :)
(this is great because now I can use the Cocoon soap client xsp
library to get the data, and plug it straight into xcml to create
a chart on the fly) :)
Essentially the IMable component exposes 1 method, getSamples()
which takes a parameter being the path to the sample requested.
ie:
instrumentable/instrumentable/instrument/sample
Separated by '/' which probably isn't a good separator.. hmm :/
I noticed that the default instrumentables you've configured include the path information mostly separated by '.' at each level, so
the actual path I have to pass is:
instrument-manager/instrument-manager.active-thread-count/instrument-manager.active-thread-count.maximum.1000.600
which contains a lot of duplicate information.
What would be great is if I could pass:
instrument-manager/active-thread-count/maximum.1000.600
as that contains the required info - instrumentable, instrument and
sample.
What prevents this from working are other '.' characters in the
string (the .1000.600 for example). What do you think about
introducing a unique separator between instruments, instrumentables
and samples when building up their names ?
Then we could also add a simple helper method to
DefaultInstrumentManager called getSamples(String path) or similar
to ease access to samples sets ?
What do you think ? Or have I misunderstood something there ?
Cheers,
Marcus
-- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
