XML Catalog Preferences
To configure options that pertain to XML Catalogs, open the Preferences dialog box and go to .
The following options are available:
- Prefer
- Determines whether public identifiers specified in the catalog are used in favor of
system identifiers supplied in the document. Suppose you have an entity in your document
that has both a public identifier and a system identifier specified, and the
catalog only contains a mapping for the public identifier (for example, a matching
public catalog entry). You can choose between the following:
- system - If selected, the system identifier in the document is used.
- public - If selected, the URI supplied in the matching public catalog entry is used. Generally, the purpose of catalogs is to override the system identifiers in XML documents, so public should usually be used for your catalogs.
Note: If the catalog contains a matching system catalog entry giving a mapping for the system identifier, that mapping would have been used, the public identifier would never have been considered, and this setting would be irrelevant. - Verbosity
- When using catalogs, it is sometimes useful to see what catalog files are parsed, if
they are valid, and what identifiers are resolved by the catalogs. This option selects
the detail level of such logging messages of the XML catalog resolver that
will be displayed in the Catalogs table at the bottom of the
window. You can choose between the following:
- None - No message is displayed by the catalog resolver when it tries to resolve a URI reference, a SYSTEM one or a PUBLIC one with the XML catalogs specified in this panel.
- Unresolved entities - Only the logging messages that track the failed attempts to resolve references are displayed.
- All messages - The messages of both failed attempts and successful ones are displayed.
- Resolve schema locations also through system mappings
-
If selected, Oxygen XML Developer Eclipse plugin analyzes both uri and system mappings to resolve the location of schema.Note: This option is not applicable for DTD schemas since the public and system catalog mappings are always considered.
- Process "schemaLocation" namespaces through URI mappings for XML Schema
- If selected, the target namespace of the imported XML Schema is resolved through the uri mappings. The namespace is taken into account only when the schema specified in the schemaLocation attribute was not resolved successfully. If not selected, the system IDs are used to resolve the schema location.
- Use default catalog
- If this option is selected and Oxygen XML Developer Eclipse plugin cannot resolve the catalog mapping with any other means, the default global catalog (listed below this checkbox) is used. For more information, see How Oxygen XML Developer Eclipse plugin Determines which Catalog to Use.
- Catalogs table
-
You can use this table to add or manage global user-defined catalogs. The following actions are available at the bottom of the table:
Add- Opens a dialog box that allows you to add a catalog to the list. You can
specify the path by using the text field, its history drop-down, the
Insert Editor
Variables button, or the browsing actions in the 
Browse drop-down list. 
Edit- Opens a dialog box that allows you to edit an existing catalog. You can
specify the path by using the text field, its history drop-down, the Insert Editor
Variables button, or the browsing actions in the Browse drop-down list.
Delete- Deletes the currently selected catalog from the list.
Up- Moves the selection to the previous resource.
Down- Moves the selection to the following resource.
Note: When you add, delete, or edit a catalog in this table, you need to reopen the currently edited files that use the modified catalog or run a manual Validate action so that the changes take full effect.You can also add or configure catalogs at framework level from the Catalogs tab in the Document Type configuration dialog box.