[ http://issues.apache.org/jira/browse/COCOON-1857?page=all ]
Brian Vargas closed COCOON-1857:
--------------------------------
Resolution: Fixed
That fix from rev 412304 works on 2.1.7, so it seems reasonable that it will
work on later versions, as well.
As a warning to any other weird-os like me out there who need this for 2.1.7,
the patch can be obtained at the URL below, but it will fail on hunk 3. The
patch is pretty trivial to apply manually, though.
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/CocoonComponentManager.java?r1=400362&r2=412304&view=patch
Also, your solution was far more elegant than mine. Thanks for your help,
Carsten!
> 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
