Stax validating xml 6
JAXP 1.0, then called Java API for XML Parsing, was a box office hit in the developer community, because of the pluggability layer provided by JAXP; that's what the essence of JAXP is.Developers can write program independent of the underlying XML processor by using the JAXP APIs, and can replace the underlying XML processor by choice without even changing a single line of application code. First of all, there has been some confusion in the past about the P in JAXP: Parsing or Processing?To transform an XML document using JAXP, you need to create a Transformer using the stylesheet.Once a Transformer is created, it takes the XML input to be transformed as a JAXP Source, and returns the transformed result as a JAXP Result.start Document is called only once before reporting any other event.Similarly, end Document is called only once after the entire XML is parsed successfully. SAXParser Factory spfactory = SAXParser Instance(); Namespace Aware(true); SAXParser saxparser = SAXParser(); //write your handler for processing events and handling error Default Handler handler = new My Handler(); //parse the XML and report events and errors (if any) to the handler saxparser.parse(new File("data.xml"), handler); DOM parsing is an object-based parsing mechanism, which generates an XML object model: an inverted tree-like data structure, which represents the XML document.But as mentioned earlier, surely it would be loaded so that any entity references can be expanded properly.
Sun Microsystems Inc., at that time had just formalized the Java Community Process (JCP), and the first version of JAXP (JSR-05) was made public in early 2000, supported by industry majors like (in chronological order) BEA Systems, Fujitsu Limited, Hewlett-Packard, IBM, Netscape Communications, Oracle, and Sun Microsystems, Inc.
But, there is a different JSR (#173) filed for pull parsing, also known as Streaming API for XML (St AX) parsing, and nothing much can be done about that now. SAX APIs were proposed by David Megginson (in early 1998) as an effort towards a standard API for event-based parsing of XML (read the genesis of SAX here).
Even though SAX is not a W3C REC, it is surely the de facto industry standard for parsing XML documents.
Because JAXP 1.0 supported only parsing, therefore, it was called Java API for XML Parsing.
But in JAXP 1.1 (JSR-63), XML transformation was introduced using XSL-T.