Validating web xml
The W3C XML specification states that a program should stop processing an XML document if it finds an error.The reason is that XML software should be small, fast, and compatible.Identifying and resolving errors in your project can be time consuming and frustrating.Fortunately, Oxygen provides functions that make error identification fast and easy.Many formation errors are easy to spot in the syntax highlighting, so you can easily correct obvious errors on-the-fly.However, there will be other cases when it will be beneficial to perform formal validation on your documents.However, you can use custom validation scenarios in Oxygen to validate the master XSLT stylesheet that includes this module and there will be no such error.
The editor uses heuristics to open a file using the best interpretation of the tagging that it can.
By default, the validation of a document is done by using a processor (XML parser, XSLT transformer, XQuery engine, etc.) to analyze the current file.
The validation scenario allows you to specify a set of files to validate, the processor to use for each file, and whether or not to perform continuous validation.
For instance, you can have an XSLT stylesheet that makes a reference to a named template or variable that is not defined in the current file, but it is defined in the Master File that includes the XSLT stylesheet.
In this case, if you validate the XSLT module by itself, you will get an error that no template or variable exists with that name.