Quoting Chris Ward <[EMAIL PROTECTED]>: > Bruno, I understand the switch from SAX 1 to 2. I have been using SAX 2 for > some time, but don't follow the switch of parsers. What was the reason for > the switch?
iText only needs a parser in a few XML-classes. For most classes the SAX API is sufficient. In my own applications I don't use the 'easy' classes with the 'built-in' parser. I choose my own parser (Xerces). > Is it because of Java 1.4 including the Jaxp XML classes? Yes. It's easier to say people need the j2ee.jar than this or that version of Xerces. > I guess I had heard that the Xerces project was faster? Rumor? I don't know why I always prefered Xerces before JAXP. The reason for the swap was just practical. In the future I hope to be able to do something with JDOM. If you don't know it yet. Look it up. It's a lot more elegant than any other XML library I know. Bruno ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
