3-6 Programming XML for Oracle WebLogic Server
Here is a reference that uses both the public and system identifier; note that the keyword SYSTEM is omitted:
DOCTYPE application PUBLIC -Sun Microsystems, Inc.DTD J2EE Application 1.2EN
http:java.sun.comj2eedtdsapplication_1_2.dtd
3.2.9 Using the WebLogic Server Entity Resolution Features
Use the following WebLogic Server features to improve the performance of external entity resolution in your XML applications:
■
Permanently store a copy of an external entity on the computer that hosts the WebLogic Administration Server.
■
Specify that WebLogic Server automatically retrieve and cache an external entity that resides in an external repository that supports an HTTP interface, such as a
URL. You can specify that WebLogic Server cache the entity either in memory or on disk and specify when the cached entry becomes stale, at which point
WebLogic Server automatically updates the cached entry.
Using the retrieve-and-cache feature, you do not have to actually copy the external entity to the local computer. The XML application refers to the actual external
entity only at specified time intervals, rather than each time the document is parsed, thus potentially greatly improving the performance of your application
while also keeping as up to date with the latest external entity as desired.
You use the XML Registry to create entity resolution entries to identify where the external entry is located locally or at a URL and what the caching options are for
entities on the Web. You identify the external entity entry using a system or public identifier. Then, in your XML document, when you reference this external entity,
WebLogic Server fetches the local copy or the cached copy whichever you have configured when parsing the document.
For detailed information on creating external entity registries with the XML Registry, refer to
Section 9.3, External Entity Configuration Tasks.
3.2.10 Using Parsers Other Than the Default
If you use JAXP to parse your XML documents, the WebLogic Server XML Registry which is configured through the Administration Console offers the following
options:
■
Accept the default parser as the server-wide parser.
■
Configure another parser of your choice such as a different version of the Apache Xerces parser as the server-wide parser.
■
Configure a parser for a particular XML document type, based on its system or public identifier, or its root element.
For instructions on how to use the XML Registry to configure parsing options, see Section 9.2, XML Parser and Transformer Configuration Tasks.
3.3 Generating New XML Documents
