Documentbuilderfactory setvalidating java www nigeriadating com
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?
JAXP supports Object-based and Event-based parsing. In Object-based, only W3C DOM parsing is supported so far.
Maybe in future versions of JAXP, the EG might decide to support J-DOM as well. Another Event-based parsing called Pull Parsing, should have been made part of JAXP.
July 6, 2005 Rahul Srivastava After the first release of the W3C XML 1.0 recommendation in early 1998, XML started gaining huge popularity.
If the application needs to be informed of the parsing events (and process it), it must implement the sax.
Thereafter, JAXP has evolved to an extent, where now it supports a lot more things (like validation against schema while parsing, validation against preparsed schema, evaluating XPath expressions, etc.,) than only parsing an XML document.
So, JAXP is a lightweight API to process XML documents by being agnostic of the underlying XML processor, which are pluggable.
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.