Hmm...I see. The guy who gave this project to me is misinformed. I was told Xalan itself is a parser but apparently it's not. I was also told Xerces is the parser recommended as a replacement for Xalan in Java 1.5. That is apparently wrong too since Xerces is the replacement for Crimson. Correct me if I'm wrong.
The point of this whole thing was to see if Xerces would cut down on the time it takes to process a 500mb XML file and pass through about 13 XSLs. What would be the optimal way (if there is one) to do this if I'm not using Xalan? In any case, now I don't see what the point is of removing Xalan from the equation and just using Xerces. It seems like all I would be doing is removing the ability to do XSL transforms in a simplified way. Doesn't Xalan use the Xerces implementation by default as the parser? Michael Glavassevich-3 wrote: > > Most XSLT processors bulid some data model of the document regardless of > the form of the input. So even if you fire SAX events to the XSLT > processor > I would expect that you would still run out of memory for very large > documents. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] > -- View this message in context: http://www.nabble.com/Parsing-a-large-XML-file-in-Xerces-tp21572644p21606335.html Sent from the Xerces - J - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
