- Revision
- 1526
- Author
- mauro
- Date
- 2010-01-20 10:03:01 -0600 (Wed, 20 Jan 2010)
Log Message
Clarified use of scenario class in file-based reporting.
Modified Paths
Diff
Modified: trunk/core/distribution/src/site/content/reports.html (1525 => 1526)
--- trunk/core/distribution/src/site/content/reports.html 2010-01-18 19:50:46 UTC (rev 1525) +++ trunk/core/distribution/src/site/content/reports.html 2010-01-20 16:03:01 UTC (rev 1526) @@ -78,6 +78,15 @@ (where <b>format</b> is any of <b>txt,html,xml</b> in the example above).</p> +<span class="followup">The file-based print stream factory for the scenario reporting requires the scenario class to +be provided in order to derive from it the output file paths (with the appropriate format extension). +If you want to migrate multiple scenarios to using file-based reporting, an intermediate stepping stone might be +to provide as a scenario class the parent class in which you build the scenario reporter (TraderScenario.class in the example), +which will result in all reporting (for a given format) to be appended to the same file. +Then gradually you can refactor your scenario classes to provide their class to the parent (as the example shows). Otherwise, +you may want to keep output in a single file, the choice is yours. +</span> + <p>The builder provides defaults for all the formats supported, but if the user needs to create a bespoke instance of a reporter for a given format, it can be easily done by overriding the default. E.g. to
To unsubscribe from this list please visit:
