Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 23 Mar 2004 17:43:49 -0000
Message-ID: <20040323174349.15756.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27875] New:  -
    Profiling data not saved with internal pipelines

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27875>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27875

Profiling data not saved with internal pipelines

           Summary: Profiling data not saved with internal pipelines
           Product: Cocoon 2
           Version: 2.1.4
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: blocks
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: fechner@werum.com


When processing an internal pipeline, the 'processXMLPipeline' or
'processReader' methods of the AbstractProcessingPipeline are invoked instead of
the 'process' method. These methods are not oberwritten by the
Profiling...Pipeline classes and therefore no profiling data will be saved. The
fix is straightforward: Copy the 'process' method, rename it and replace the
calls to super.process with super.processXMLPipeline resp. super.processReader.
I've done it within my testing environment and it works fine.