Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.1.4
-
None
-
None
-
Operating System: All
Platform: PC
-
27875
Description
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.
'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.