cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <>
Subject [jira] Commented: (COCOON-1857) Sitemap Components Do Not Appear in Instrumentation
Date Wed, 07 Jun 2006 06:29:30 GMT
    [ ] 

Carsten Ziegeler commented on COCOON-1857:

Thanks Brian for the investigation!
We shouldn't change ExcaliburComponentManager - the code is outside of Cocoon, so we should
try to find a "cocoon only" solution if possible. As far as I can see, Cocoon always uses
a CocoonComponentManager; the root manager is setup in the Cocoon class and gets the instrumentation
manager set there. So we can hopefully fix this in the CocoonComponentManager class.
I just added a possible fix for this to the 2.1.x branch - can you please review this and
see if it works for you (and then close this issue)?


> Sitemap Components Do Not Appear in Instrumentation
> ---------------------------------------------------
>          Key: COCOON-1857
>          URL:
>      Project: Cocoon
>         Type: Bug

>   Components: - Components: Sitemap
>     Versions: 2.1.9
>     Reporter: Brian Vargas
>     Assignee: Carsten Ziegeler

> Although I have correctly added Excalibur instrumentation code to custom sitemap components,
those components never show up when connecting with the instrumentation client.
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message