mjdenham wrote: > Alternatively are there any other options? At Ghent University, we create invoices the way you describe. We have one large XML containing all the possible clauses: students that are enrolled full-time, half-time, students that combine courses,... I guess we have about 30 possibilities + combinations.
I wrote a custom DocumentHandler, a custom PageEvent and a class that gets data from the database to find out which clauses apply (it also keeps data to replace tags like <studentname />). The XML is parsed using SAX and my custom handler knows which custom tags correspond with which iText objects. If you have the book about iText, you'll see I use this technique in some of the book examples too. br, Bruno ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
