The material in this chapter builds on the prototype code developed in Chapter 5. It assumes you have completed all the instructions in Chapter 5 and that everything up to the event-triggered matching logic works as expected. At this point, your ADF in the music store application's source directory, C:\SQL-NS\Samples\MusicStore\SongAlerts, should contain the same code as the final supplementary ADF, ApplicationDefinition-4.xml, in C:\SQL-NS\Chapters\05\SupplementaryFiles. Just as in Chapter 5, I've provided supplementary ADFs that contain the new code shown in this chapter. As you go through the code listings, you can either type the new code manually or use these supplementary ADFs. Table 6.1 lists the supplementary ADFs for this chapter. You'll find these files in this chapter's source directory, C:\SQL-NS\Chapters\06\SupplementaryFiles.
The instructions provided in Chapter 5 for adding code to the ADF and then updating the music store instance still apply. You should already be familiar with these instructions from the work you did in Chapter 5. The only difference is that if you're using the supplementary ADFs, you'll copy them from the Chapter 6 supplementary files directory C:(\SQL-NS\Chapters\06\SupplementaryFiles) instead of the Chapter 5 supplementary files directory. You will still be copying these files to the same location, overwriting the music store application's ADF at C:\SQL-NS\Samples\MusicStore\SongAlerts\ApplicationDefinition.xml. For reference, you can find the full instructions in the "Adding Code to the ADF" section (p. 130) and "Making Updates to an Instance and Its Applications" section (p. 131) of Chapter 5. |