Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

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 10 Next »

Features

Any XML file can be validated with this plugin.The plugin provides static code analysis of XML files within Sonar. Typical use cases are validation of files for coding or usability standards. 

The following functionality is provided:

  • XML validation
  • XML schema validation
  • Configurable rules using XPath
  • sizing (files, lines of code)

The XML validation is available out-of-the box. The configurable XPath rules requires some knowledge of XPath.

The plugin scans the following files by default: .xml, .xhtml. The file extensions and the file inclusion patterns are configurable. 

The plugin imports the XML files in Sonar, and performs the validations. The checks are configurable in the Sonar rules repository. 

Use Cases

Typical use cases:

- validation of XHTML files

By using the XHTML schemas as provided by the W3C (strict, transitional, and others) quickly validate the markup of a set of XHTML files. 

- validation of XML files

Validate a set of XML files for conformance to the provided XML schema. 

- Validate rules in XML files 

e.g. validate the maven pom files for conformance to coding standards.

Configuration

The following properties of the plugin are configurable:

property

description

default value

sonar.xml.sourceDirectory

folder that will be scanned (relative to project root)

 

sonar.xml.fileExtensions

file extensions that will be scanned

xml, xhtml

sonar.xml.includeFileFilter

additional filter for the files to be scanned

 

sonar.xml.schemas

namespace of schema to use for validation

 

The properties may be set in sonar, the maven pom or the maven commmandline.

Usage & Installation

Installation

  1. Copy the jar into /extensions/plugins/ directory
  2. Restart Sonar Web server

Analysis
Create a maven pom for your project. Set the following properties:

  • sonar.language: xml
  • sonar.xml.sourceDirectory: [folder of the xml files]
  • sonar.dynamicAnalysis: false

Schema Validation

Schemas

Schema validation is performed by the xerces parser using XML schemas (XSDs). The plugin has a couple of schema's available:

namespace or short name

Doctype

Description

http://www.w3.org/2001/xml.xsd

 

XML

http://www.w3.org/1999/xhtml

 

XHTML1.0 Strict

xhtml1-strict

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

XHTML1.0 Strict

xhtml1-transitional

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

XHTML1.0Ttransitional

xhtml1-frameset

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

XHTML1.0 Frameset

 

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

XHTML1.1

http://java.sun.com/jsf/core

 

JSF core

http://java.sun.com/jsf/html

 

JSF HTML Basic

http://java.sun.com/jsf/facelets

 

JSF Facelets

http://maven.apache.org/POM/4.0.0

 

Maven Project Model

You can use the names in the first column to identify the schema for validation, e.g. sonar.xml.schemas=xhtml1-transitional

If you need to check with another schema, you can provide the path to the schema. The plugin will search for the schema on filesystem using a relative path. 

Check

The rules profile contains the check XmlSchemaCheck. This check can be copied and instantiated multiple times. 

The check has two properties: 

property

description

default value

sonar.xml.sourceDirectory

folder that will be scanned (relative to project root)

 

sonar.xml.fileExtensions

file extensions that will be scanned

xml, xhtml

filePattern

filter for the files to be validated with this check

 

schemas

namespace of schema to use for validation

e.g. xhtml1-strict or schemas/xsd/mycustomschema.xsd

If you specify schemas=autodetect the parser will try to load the schema based on the doctype or the namespace declaration in the document.

There are quite a few checks related to XML validation. These are grouped in three categories:

XPath Rules

content to be provided

Examples

XHTML validation

Sample pom file:

With this pom, you can simply call mvn:

Maven POM Validation per project

Recursively check the pom file in a project and its subprojects. 

sourceDirectory is set to . means all files in the project are scanned.
includeFileFilter specifies to scan only pom.xml files (relative path to project root). So only the pom file in the current project will be scanned. 
schemas is set to maven namespace so all pom files will be validated with the maven xml schema.

Maven POM Validation (quick)

Quickly validate all pom files in a project and its subprojects. 

-N is specified so only the root project will be analyzed by maven.
sourceDirectory is set to . means all files in the project are scanned.
includeFileFilter specifies to scan all pom.xml files. With this filter, also pom files in child modules will be scanned. 
schemas is set to maven namespace so all pom files will be validated with the maven xml schema.

Plugin Architecture

The plugin uses the Xerces library for parsing and validation.  

http://xerces.apache.org/xerces-j/

Changelog

Loading

Release 0.1 (3 issues)

  • No labels