CocoonCompnentManager Fails to Set InstrumentManager

[Brian Vargas <ar...@procrastinators.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hi,

I am attempting to add some instrumentation code to some custom sitemap
components.  (In this case, it's a reader, but I think the same problem
will occur regardless of the type of component.)  I have implemented the
instrumentation interfaces appropriately, but the component never gets
registered for instrumentation.

Specifically, the behavior we are seeing is that setInstrumentableName()
gets called on our custom reader, as expected, but then neither
getInstruments() nor getChildInstrumentables() ever gets called.

Tracing through some code, it seems that the proximate cause of this is
that the CocoonComponentManager, extending ExcaliburComponentManager,
never has its m_instrumentManager member set to the m_instrumentManager
value of its parent ComponentManager instance.  After some thought, it
appears that the Excalibur Instrumentation interfaces make it really
difficult to get an InstrumentManager from a ComponentManager, thus
making it really hard to initialize the concrete child
ComponentManager's instrumentation.

Any thoughts on what an appropriate course of action might be?  Am I
over-thinking this?  Is the InstrumentManager hidden in context
someplace that I could just use?  I appreciate the help!

Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: What is this? http://pgp.ardvaark.net

iD8DBQFESTSm3YdPnMKx1eMRA29bAKCncH6UTcbtDm2U8EeBhXsddPWvhwCgwVlO
IFA+EF9D5Ctnz052ZVExWiY=
=/I03
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org