Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

Description / Features

This plugin enables analysis of XML files within Sonar.

Some common use cases are:

  • Validation of XHTML files against schemas provided by the W3C (strict, transitional, and others)
  • Validation of XML files against a provided XML schema
  • Validation of rules in XML files (ex: validate the Maven pom files against coding standards)


  1. Install the XML plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server


Run a Sonar Analysis with the Sonar Runner (Recommended Way)

To launch a Sonar analysis of your XML project, use the Sonar Runner.

A sample project is available on github that can be browsed or downloaded: /projects/languages/xml/xml-sonar-runner.

Run a Sonar Analysis with the other Analyzers

Maven and Ant can also be used to launch analysis on XML projects.

Validating Files Against Specific Schemas

Files can be validated against specific schemas thanks to the XML Schema Check rule.

Within the same project some files can be validated against schema 'S1', others against schema 'S2', others against schemas 'S3' and 'S4', and so on. So, this rule has to be copied and configured as many times as you have pairs of files/schema.




Files to be validated against the schemas set through the schemas parameter.


Whitespace-separated list of schemas to use for validation.

It can either be set to:

  • a built-in schema (ex: xhtml1-strict)
  • or a URL (ex:
  • or a relative path to a schema on the filesystem (ex: schemas/xsd/mycustomschema.xsd)

Default value: autodetect. In this case, the parser will try to load the schema based on the doctype or the namespace declaration in the document.

Built-in schemas:

Namespace or Short name






XHTML1.0 Strict


-//W3C//DTD XHTML 1.0 Strict//EN

XHTML1.0 Strict


-//W3C//DTD XHTML 1.0 Transitional//EN

XHTML1.0 Transitional


-//W3C//DTD XHTML 1.0 Frameset//EN

XHTML1.0 Frameset


-//W3C//DTD XHTML 1.1 Strict//EN



JSF Core




JSF Facelets


Maven Project Model


  • Schema validation is performed by the Xerces parser using XML schemas (XSDs).
  • For validation of XHTML files it is recommended to use autodetect, xhtml1-transitional or xhtml1-strict.

Custom Checks Using XPath Expressions

The XPath Check rule allows to define custom checks on XML documents using XPath expressions.

Within the same project some files can be checked against XPath rules 'R1', 'R2', etc., others against rules 'R6', 'R7', etc. and so on. So, this rule has to be copied and configured as many times as you have pairs of files/rule.




This rule allows to define some homemade XML rules with help of an XPath expression.

Violations are created depending on the return value of the XPath expression. If the XPath expression returns:

  • a single or list of AST nodes, then a line violation with the given message is created for each node
  • a boolean, then a file violation with the given message is created only if the boolean is true
  • anything else, no violation is created

Here is an example of an XPath expression to log a violation on each 'td' tag using the 'nowrap' deprecated attribute: //td[@nowrap]


Files to be checked against the XPath expression set through the xpathQuery parameter.

xpathQuery The XPath query
messageThe violation message

Change Log


Release 1.0 (not yet released) (15 issues)



Release 0.2 (9 issues)



Release 0.1 (3 issues)

  • No labels