xSVN

xSVN is a modified Subversion in a way that the former uses Berkeley DB XML (DB XML) for storing XML files. Storing XML files in the DB XML allows us to take advantages of all features DB XML has, and in combination with versioning achieve even more. For more information refer to  Balisage paper, but on this page we describe some xSVN specific use cases:

1. If in xSVN commit one of XML files are ill-formed, then the whole xSVN transaction is aborted. A user has to fix the ill-formed XML file, or make it non-XML (see next item), then try to commit again
2. How does xSVN recognize what files are considered to be XML? By default, xSVN treats following files as XML:
   • A file has an extension *.xml, *.omdoc or *.xhtml
   • A file has an svn svn:mime-type property: text/xml, text/xml+omdoc, application/xml or application/omdoc+xml
3. In order to overwrite default setting of XML files recognition, a user has to modify ~/.subversion/servers file, where ~ is the home folder of a user under which xSVN in being run. If xSVN is used in Apache, then the home folder of a user that runs Apache child processes is used. In addition to standard SVN setting, the servers file may contain the following options under the [global] section:
   • tnt.ignore-all Maybe yes or no. If set to yes, then all files will be considered as non-XML. Default value is no
   • tnt:files The semicolon (;) separated list of file patterns. For instance, *.xslt;papers*.docbook
   • tnt:mime-types The semicolon (;) separated list of file mime-types. For instance, application/html;text/html
4. tntbase:validate property can be set on files or folders to enable simple or advanced validation (see the page about validation for more details)