Validator.nu Pipeline Overview - Revision history

MikeSmith at 04:30, 29 December 2016

2016-12-29T04:30:27Z

← Older revision		Revision as of 04:30, 29 December 2016
Line 1:		Line 1:
	{{Obsolete\|spec=https://github.com/validator/validator/wiki/~~Service:-~~System-~~backend:~~-Pipeline}}		{{Obsolete\|spec=https://github.com/validator/validator/wiki/System-»-Pipeline}}
	Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.		Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.

MikeSmith at 01:19, 22 March 2015

2015-03-22T01:19:32Z

← Older revision		Revision as of 01:19, 22 March 2015
Line 1:		Line 1:
	{{Obsolete\|spec=https://github.com/validator/validator/wiki/Pipeline~~-overview~~}}		{{Obsolete\|spec=https://github.com/validator/validator/wiki/Service:-System-backend:-Pipeline}}
	Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.		Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.

MikeSmith at 14:30, 17 March 2015

2015-03-17T14:30:18Z

← Older revision		Revision as of 14:30, 17 March 2015
Line 1:		Line 1:
			{{Obsolete\|spec=https://github.com/validator/validator/wiki/Pipeline-overview}}
	Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.		Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.

Hsivonen: /* Output Pipeline */ No longer using the Xalan serializer

2008-09-09T09:02:09Z

Output Pipeline: No longer using the Xalan serializer

← Older revision		Revision as of 09:02, 9 September 2008
Line 36:		Line 36:

	# <code>nu.validator.messages.XhtmlMessageEmitter</code> (extends <code>MessageEmitter</code>)		# <code>nu.validator.messages.XhtmlMessageEmitter</code> (extends <code>MessageEmitter</code>)
	# <code>nu.validator.htmlparser.sax.HtmlSerializer</code> (HTML) / ~~Xalan Serializer~~ (XHTML)		# <code>nu.validator.htmlparser.sax.HtmlSerializer</code> (HTML) / <code>nu.validator.htmlparser.sax.XmlSerializer</code> (XHTML)
	# <code>java.io.OutputStream</code>		# <code>java.io.OutputStream</code>

Line 42:		Line 42:

	# <code>nu.validator.messages.XmlMessageEmitter</code> (extends <code>MessageEmitter</code>)		# <code>nu.validator.messages.XmlMessageEmitter</code> (extends <code>MessageEmitter</code>)
	# ~~Xalan Serializer~~		# <code>nu.validator.htmlparser.sax.XmlSerializer</code>
	# <code>java.io.OutputStream</code>		# <code>java.io.OutputStream</code>

Hsivonen: Create page

2008-02-13T10:04:18Z

Create page

New page

Validator.nu makes extensive use of SAX pipelines. When a document is being validated, the main processing loop is in the parser that pulls data from the <code>InputStream</code> and pushes out parse events.

These events are pushed through a pipeline of filters. Then each parse event is repeated to each validator in a chain of side-by-side validators. The parser, the filters and the validators push messages to a SAX <code>ErrorHandler</code>. In the cases of the HTML, XHTML and XML output formats, the <code>ErrorHandler</code> implementation in turn pushes out SAX events corresponding to the generated result document.

==Parser Pipeline==

===HTML Pipeline===

# <code>nu.validator.htmlparser.sax.HtmlParser</code> (in streaming mode)
# <code>nu.validator.xml.WiretapXMLReaderWrapper</code> (feeding each event first to <code>nu.validator.source.LocationRecorder</code>)
# <code>nu.validator.xml.AttributesPermutingXMLReaderWrapper</code>
# Validators

===XML Pipeline===

# <code>nu.validator.gnu.xml.aelfred2.SAXDriver</code>
# <code>nu.validator.xml.IdFilter</code>
# <code>nu.validator.xml.WiretapXMLReaderWrapper</code> (feeding each event first to <code>nu.validator.source.LocationRecorder</code>)
# <code>nu.validator.xml.NamespaceDroppingXMLReaderWrapper</code> (if there are namespaces to be filtered out)
# <code>nu.validator.xml.AttributesPermutingXMLReaderWrapper</code>
# <code>nu.validator.servlet.RootNamespaceSniffer</code> (if schema was left to autodetect)
# Validators

==Validator Chain==

All (schema-based and non-schema-based) validators have to implement <code>com.thaiopensource.validate.Validator</code>. Non-schema-based checkers inherit from <code>org.whattf.checker.Checker</code> and are wrapped in <code>org.whattf.checker.jing.CheckerValidator</code> to implement the required interface.

When more than one schema is specified, the corresponding validators are chained using <code>com.thaiopensource.relaxng.impl.CombineValidator</code>.

==Output Pipeline==

# <code>nu.validator.messages.MessageEmitterAdapter</code> (implements <code>ErrorHandler</code>)
# <code>nu.validator.messages.MessageEmitter</code>

===HTML and XHTML===

# <code>nu.validator.messages.XhtmlMessageEmitter</code> (extends <code>MessageEmitter</code>)
# <code>nu.validator.htmlparser.sax.HtmlSerializer</code> (HTML) / Xalan Serializer (XHTML)
# <code>java.io.OutputStream</code>

===XML===

# <code>nu.validator.messages.XmlMessageEmitter</code> (extends <code>MessageEmitter</code>)
# Xalan Serializer
# <code>java.io.OutputStream</code>

===JSON===

# <code>nu.validator.messages.JsonMessageEmitter</code> (extends <code>MessageEmitter</code>)
# <code>nu.validator.json.JsonHandler</code>
# <code>java.io.OutputStream</code>

===GNU===

# <code>nu.validator.messages.GnuMessageEmitter</code> (extends <code>MessageEmitter</code>)
# <code>java.io.OutputStream</code>

===Text===

# <code>nu.validator.messages.TextMessageEmitter</code> (extends <code>MessageEmitter</code>)
# <code>java.io.OutputStream</code>

[[Category:Validator.nu Documentation]]