Changes

Jump to navigation Jump to search
1,205 bytes added ,  11:26, 24 January 2011
no edit summary
Fetching the <code>xhtml1-strict.dtd</code> obviously involves some network traffic. When dealing with single files this may seem tolerable, but
importing large collections might benefit from caching these resources locally. Users report Depending on your connection you will experience significant improvements.
== XML Entity and URI Resolvers in BaseX ==
</catalog>
</pre>
This rewrites all SystemId that start SystemIds starting with: ''<nowiki>http://www.w3.org/TR/xhtml1/DTD/</nowiki>'' to ''file:///path/to/dtds/''.
The XHTML DTD <code>xhtml1-strict.dtd</code> and all its linked resources will now be loaded from the specified path.
===GUIMode===[[File:catalog-file.jpg|thumb|Location for the Catalog File]]When running BaseX in GUI modesimply provide the path to your XML Catalog file in the '''Parsing'''-Tab of the Database Creation Dialog. ===Console & Server Mode===To enable Entity Resolving in Console Mode specify the following [[options]]:* <code>SET CATFILE [path]</code>Now entity resolving is active for the current session. All subsequent <code>ADD</code> commands will use the catalog file to resolve entities. '''Please note''' that entity resolving only works with option: <code>SET INTPARSE false</code>. <code>INTPARSE</code> is set to false by default. == Using other Resolvers ==There might be some cases when you do not want to use the built-in resolver that Java provides by default (via <code>com.sun.org.apache.xml.internal.resolver.*</code>). BaseX offers support for the Apache maintained [http://xml.apache.org/commons XML Commons Resolver] available for download [http://xerces.apache.org/mirrors.cgi here].To use it add '''resolver.jar''' to the classpath when [[Startup|starting BaseX]]:<pre class="brush:bash">java -cp basex.jar:resolver.jar org.basex.BaseXServer</pre>
administrator, Bureaucrats, editor, Interface administrators, reviewer, Administrators
401

edits

Navigation menu