In all cases, the
audit code will be a five-digit number. The first digit of this number is either 1 if an audit is being added by
OrderProcessor or 2 if the audit is added by a pipeline section. The next two digits are used for the pipeline
stage that added the audit (which maps directly to the status of the order when the audit was added). The final
two digits uniquely identify the message within this scope. For example, so far we??™ve seen the following codes:
??? 10000: Order processor started
??? 10001: Order processor finished
??? 10002: Order processor error occurred
Later, we??™ll see a lot of these codes that start with 2, as we get on to the pipeline sections and include the necessary
information for identifying the pipeline section as noted previously.We hope you??™ll agree that this scheme allows for
plenty of flexibility, although we can, of course, use whatever codes we see fit. As a final note, codes ending in 00
and 01 are used for starting and finishing messages for both the order processor and pipeline stages, whereas 02
and above are for other messages. There is no real reason for this apart from consistency between the components.
The PsDummy class that is used in this skeleton processor performs some basic functions to check that things are
working correctly:
class PsDummy implements IPipelineSection
{
public function Process($processor)
{
$processor->CreateAudit('PsDoNothing started.
Pages:
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703