Apache Cocoon has the capability to utilise an entity resolution mechanism.
External entities (e.g. Document Type Definitions (DTDs), character entity
sets, XML sub-documents) are resources that are declared by an XML instance
document - they exist as separate objects. An entity catalog assists with
entity management and the resolution of entities to accessible resources.
It also reduces the necessity for expensive and failure-prone network
retrieval of the required resources.
"Entities" represent the physical structure of an XML instance document,
whereas "elements" represent the logical structure. The complete entity
structure of the document defines which pieces need to be incorporated, so
as to build the final document. Those entities are objects from some
accessible place, e.g. local file system, local network, remote network,
generated from a database. Example entities are: DTDs, XML sub-documents,
sets of character entities to represent symbols and other glyphs, image
So how are you going to define the accessible location of all those pieces?
How will you ensure that those resources are reliably available? Entity
resolution catalogs to the rescue. These are simple standards-based
plain-text files to map public identifiers and system identifiers to local
or other resources.
Do you wonder why we cannot use the sitemap to resolve these resources?
This is because the resolution of all entities that compose the XML
document is under the direct control of the guts of the parser and the XML
structure. The parser has no choice - it must incorporate all of the defined pieces. If it cannot retrieve them, then it is broken and reports an error.
With the powerful catalog support there are no such problems. This document
provides the following sections to explain Cocoon capability for
resolving entities ...
The following article eloquently describes the need for all parsers and
XML frameworks to be capable of utilising entity resolvers.
"If You Can Name It, You Can Claim It!"
by Norman Walsh. Please read that document, then return here to apply
entity catalogs to Cocoon.
(Note: That article (and Java classes) evolved to become the
resolver.zip Java package that has been added to Cocoon
- a more recent version of the article is available at the XML Commons site
(see below). The API javadocs for
resolver have further information.
However, you do not need to know the gory details to understand catalogs
and configure them.)
This snippet from an XML instance shows the Document Type Declaration.
Notice that it declares its ruleset, the Document Type Definition (DTD),
as an external entity. Notice also that the resource is network-based.
<!DOCTYPE article PUBLIC "-//OASIS//DTD Simplified DocBook XML V18.104.22.168//EN"
... content goes here
Now consider what will happen when Cocoon tries to process this XML
instance. Whether you have set validation=yes or not, the parser will
still want to resolve all of the entities that are required by the XML
instance (i.e. the DTD and any other entities that the DTD might declare).
So it will happily trundle across the network to get them. It will do this
every time that the document is processed. This is obviously a needless
overhead. Worse still, what happens if that host is down or the network is
congested. Additionally, if your Cocoon is an off-line server then it is
always broken because it cannot retrieve the network-based resources.
As the Walsh document explained, the secrets to entity resolution are the
public identifiers, system identifiers, and the catalog to map between them.
Here we provide an overview and show an example catalog which we will then
use with the Demonstration #2 below.
External entity declarations
To define an external entity in an XML instance document, you must
provide an external declaration consisting of at least a
system identifier and optionally a
public identifier. The system identifier defines the
physical location of the external entity. The public identifier is a
unique symbolic name that can be used to map to a certain physical location.
Note that if you provide both a public and a system identifier, then the
public identifier is listed first and the system identifier is not
preceded by the keyword
Here are four separate examples ...
<!ENTITY pic SYSTEM "images/pic.gif" NDATA gif>
<!ENTITY % ISOnum PUBLIC
"ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML" "ISOnum.pen">
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN"
(In your XML instance document, or DTD, you would include those entities
like this ...
None of those system identifiers looks reliable or easily managed.
Use a catalog to make them so.
Simple example catalog
catalog maps public identifiers to their corresponding
physical locations. The catalog entries in an OASIS catalog are a simple
(The specification fully defines the format.)
There about a dozen different types of catalog entry - two important
- maps the public identifier
publicId to the system
- maps the system identifier
systemId to the alternate
-- this is the default OASIS catalog for Apache Cocoon --
-- ISO public identifiers for sets of character entities --
PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN//XML"
PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN//XML"
PUBLIC "ISO 9573-15:1993//ENTITIES Greek Letters//EN//XML"
PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN//XML"
PUBLIC "ISO 8879:1986//ENTITIES General Technical//EN//XML"
PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML"
-- these entries are used for the catalog-demo sample application --
PUBLIC "-//Arbortext//TEXT Test Override//EN"
PUBLIC "-//Arbortext//TEXT Test Public Identifier//EN"
PUBLIC "-//Indexgeo//DTD Catalog Demo v1.0//EN"
-- end of entries for the catalog-demo sample application --
System identifiers can use full pathnames, filenames, relative pathnames,
or URLs - in fact, any method that will define and deliver the actual
physical entity. If it is just a filename or a relative pathname, then the
Catalog Resolver will look for the resource relative to the location of
When the parser needs to load a declared entity, then it first consults
the Catalog Resolver to get a possible mapping to an alternate system
identifier. If there is no mapping for an identifier in the catalogs
(or in any sub-ordinate catalogs), then Cocoon will carry on to
retrieve the resource using the original declared system identifier.
See catalogs in action with the
intends to be self-documenting. The top-level XML instance describes its
role, and each included external entity reports how it came into being.
This example builds upon the example provided by the Walsh article.
(Tip: To see the error message that would result from not using a catalog,
simply rename the default
catalog file before starting
Here is the source for the top-level XML instance document
<!DOCTYPE catalog-demo PUBLIC "-//Indexgeo//DTD Catalog Demo v1.0//EN"
<!ENTITY testpub PUBLIC "-//Arbortext//TEXT Test Public Identifier//EN"
<!ENTITY testsys SYSTEM "urn:x-arbortext:test-system-identifier">
<!ENTITY testovr PUBLIC "-//Arbortext//TEXT Test Override//EN"
<!ENTITY % ISOnum PUBLIC
"ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML"
<!ENTITY note "Note:">
<para>This sample application demonstrates the use of catalogs for
entity resolution. ¬e; see the Apache Cocoon documentation
<link href="/cocoon/documents/catalog.html">Entity resolution with
catalogs</link> for the full background and explanation, and the XML
source of this document (test.xml).
<para>This top-level XML instance document is test.xml - it declares
three other XML sub-documents as external entities and then includes
them in the sections below. The real system identifiers will be looked
up in the catalog, to resolve the actual location of the resource.
<para>The Document Type Definition (DTD) is declared using both a public
identifier and a system identifier. The system identifier for the DTD is
a network-based resource (which is deliberately non-existent). However,
the catalog overrides that remote DTD to instead use a copy from the
local filesystem at the location defined by the catalog entry. Note that
it is via the use of a public identifier that we gain this power.
<para>The internal DTD subset of the top-level document instance goes on
to declare the three external sub-document entities using various means.
It also declares and includes the ISOnum set of character entities,
so that we can use entities like &frac12; (to represent ½).
Finally the internal DTD subset declares an internal general entity
<para>testpub ... this entity is declared with a PUBLIC identifier and a
bogus system identifier (which will be overridden by the catalog)
<para>testsys ... this entity is declared with a SYSTEM identifier
(which will be resolved by the catalog)
<para>testovr ... is declared with a PUBLIC identifier and a system
identifier (the catalog is set to not override this one, so the
declared system identifier is used)
Here is the source for one of the included sub-document external entities
<para>¬e; This paragraph is automatically included from the
testpub.xml external file.
The entity declaration deliberately used a non-existent file
as the system identifier. The catalog then used the declared
public identifer to resolve to a specific location on the local
A default catalog and some base entities (e.g. ISO*.pen character
entity sets) are included in the Cocoon distribution at
- the default catalog is automatically loaded when Cocoon starts.
If you suspect problems, then you can raise the level of the
verbosity property (to 2 or 3) and watch the messages going
to standard output when Cocoon starts and operates. You would also do
this to detect any misconfiguration of your own catalogs.
You can extend the default configuration to include local catalogs
for site-specific requirements. This is achieved via various means.
Parameters (properties) for the resolver component can be specified in the
configuration file. See the detailed internal notes - here is a precis.
... The main catalog file. Its path name is relative to the
Cocoon context directory.
... The full filesystem pathname to a single local catalog file.
... The level of messages from the resolver
(loading catalogs, identifier resolution, etc.).
It value may range from 0 (no messages), to 10 detailed log messages.
CatalogManager.properties file is included
with the distribution - modify it to suit your needs. You can add your
own local catalogs using the
(See the notes inside the properties file).
The build process will automatically copy the properties file from
thereby making it available to the Java classpath.
If you see an error message going to STDOUT when Cocoon starts
Cannot find CatalogManager.properties) then this means that
the properties file is not available to the Java classpath. Note that this
does not mean that entity resolution is disabled, rather that no local
configuration is being effected. Therefore no local catalogs will be
loaded and no entity resolution messages will be received (verbosity
level is zero by default).
That may truly be the intention, and not just a configuration mistake.
You can still use
Resolver directives inside your catalog file
cocoon.xconf to effect your local
The actual "catalog" files have a powerful set of directives.
For example, the CATALOG directive facilitates the
inclusion of a sub-ordinate catalog. The list of resources below will
lead to further information about catalog usage.
Example local configuration for Simplified DocBook
We use the Simplified DocBook XML DTD for some of our documentation.
Here are the few steps that we followed to configure Cocoon to be able
to process our XML instances.
Downloaded a recent copy of the Simplified DocBook DTD (the flattened DTD
will suffice) from
and place it at
Created a catalog file at
with a single entry for the Simplified DocBook XML DTD
Added the parameter (
local-catalog) to the
(using the full pathname to the
-- Catalog file (sdocbook.cat) for Simplified DocBook --
-- See www.oasis-open.org/docbook/ --
-- Driver file for the Simplified DocBook XML DTD --
PUBLIC "-//OASIS//DTD Simplified DocBook XML V22.214.171.124//EN"
-- end of catalog file for Simplified DocBook --
We could similarly configure Cocoon for the full DocBook XML DTD and
related entities. In fact, the DocBook distribution already contains a
catalog file. We need only append the pathname to our
There are a few important starting points for
further information about using and configuring
the DocBook DTDs.
Parser interface provides an
hook to allow an application to resolve the external entities. This is
The XML Commons Apache project has
which provides a CatalogResolver. This is incorporated
into Cocoon via
Default configuration is achieved via
which initialises the catalog resolver and loads a default system catalog.
ResolverImpl.java enables local
configuration by applying properties from the
CatalogManager.properties file and then further configuration
OASIS Catalogs (TR 9401:1995 Entity Management) are plain-text files
with a simple delimited format. There is also a new standard being
developed for XML Catalogs, using an xml-based structured plain-text file
(gee :-). Links to both standards are provided below. Both catalog formats
can be currently used with this entity resolver. However, the latter
standard is not yet settled. OASIS TR9401 catalogs will suffice.
There has been a recent flood of XML tools - unfortunately, many do not
implement entity resolution (other than by brute-force retrieval), so
those tools are crippled and cannot be used for serious XML processing.
Please ensure that you choose
proper XML tools
for the preparation and validation of your XML instance documents.
The default catalog that is shipped with the Cocoon distribution is
deliberately basic. You will need to supplement it with your own catalog
devised to suit your particular needs.
Most XML documents that we would want to serve with Cocoon are already
in existence in another information system. The XML document instances have
a declaration of their DTD Document Type Definition as an external file.
This external DTD also includes entity sets such as ISOnum, ISOlat1, etc.
Also the DTD declaration has a Formal Public Identifier and a System
Identifier which points to a remote URL. These XML instance documents cannot
be altered to make workaround solutions like
Entity management is effected by providing a standards-based mechanism to
resolve public identifiers and system identifiers to local filenames or
other identifiers or even to other remote network resources. So references
to external DTDs, sets of character entities such as mathematical symbols,
fragments of XML documents, complete sub-documents, non-xml data chunks
(like images), etc. can all be centrally managed and resolved locally.
Here are some links to documents which extol entity management: