[ http://issues.apache.org/jira/browse/COCOON-1857?page=comments#action_12415090 ]
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)? Thanks > Sitemap Components Do Not Appear in Instrumentation > --------------------------------------------------- > > Key: COCOON-1857 > URL: http://issues.apache.org/jira/browse/COCOON-1857 > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
