This chapter covers
The theory of pages
Page events in practice
XML ideas for iText
In the previous chapter, we talked about events triggered in Adobe Reader by the end user. This chapter discusses events of a completely different nature: events that occur on the server side while composing a document—when a document is opened (step 3 in the PDF production process) or closed (step 5), when a new page is started or ended (step 4), and so on. These events aren’t triggered by an end user or a developer, but by iText.
This functionality opens some interesting perspectives. When you add building blocks to a document, you don’t care about pages. You trust that iText will send the content to the output stream each time ...