Summary
Entity management in XML applications summary
This tutorial introduced the concept of entity management using XML catalogs. The basic model for entity management was reviewed introducing the concept of a catalog processor, which is responsible for mapping resource identifiers provided by an XML application into URI references. The application can then use these URI references to obtain the identified resources. A catalog processor typically reads several catalog files, which define mappings from identifiers to URIs. The tutorial also reviewed the advantages of extending an application to incorporate a catalog processor. These advantages included increased performance, stability, security, and interoperability.
The XML Catalog specification describes a standard format for catalog files that allows mappings from identifiers to URI references to be declared. The format supports both explicitly defined mappings and a simple rewriting mechanism. XML catalogs may also be partitioned up into several individual catalog entry files that collectively form a single logical catalog. I provided example catalog files and illustrated their use with a simple command-line application.
Finally, the tutorial introduced the XML Resolver API, which can be used to extend an
XML application with support for the XML Catalog specification. The API provides an
implementation of the two key interfaces used to resolve identifiers and URIs in the
JAXP application. Example code demonstrated the use of the
EntityResolver and URIResolver interfaces.
The concept of entity management is often overlooked by XML developers but it can greatly improve application performance and flexibility. Indeed, supporting XML catalogs should be considered a best practice among XML developers.


