Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
<syntaxhighlight lang="xquery">
-Djavax.xml.catalog.resolve=continue
Q{java:System}setProperty('javax.xml.catalog.resolve', 'continue')
</syntaxhighlight>
no edit summary
With BaseX 10, all whitespaces are now preserved when importing XML resources, unless whitespace stripping is enabled.
The notorious {{Code|CHOP}} option was removed to prevent conflicting behavior caused by earlier installations. It was replaced by a new {{CodeOption|STRIPWS}} option, which defaults to {{Code|false}}. In addition, the new default of the [[Serialization|serialization parameter]] {{Code|indent}} is {{Code|no}}.
Please be warned that the new default can throw off existing applications. If you want to restore the old behavior, you should assign the following values in your [[Configuration|.basex configuration file]], or the {{Code|web.xml}} file of your [[Web Application]]:
<rest:databases xmlns:rest="http://basex.org/rest"/>
<!-- before after -->
<databases xmlns="http://basex.org/rest"/>
</syntaxhighlight>
=Catalogs=
From early on, catalog resolvers had been neglected both in BaseX and Java. This has changed: The new [https://docs.oracle.com/en/java/javase/11/core/xml-catalog-api1.html XML Catalog API] from Java is now universally used to resolve references to external resources. As an alternative, Norman Walsh’s [https://xmlresolver.org/ Enhanced XML Resolver] will be used is utilized if it is found in the classpath.
The option for supplying the XML catalog was renamed from <code>CATFILE</code> to {{Option|CATALOG}}. See [[Catalog Resolver]] for more details.
=Graphical User Interface=
