Chapter 36: Configuring Java XML Parser Support
JAXP provides a plugin model for XML parser classes. You can configure the parser implementation used by your application code. A JAXP 1.1 properties window will appear in each of the following EAServer Manager configuration modules:
Web Application Properties
Application Client Properties
The JAXP properties window allows you to choose which JAXP factory implementation to use for the SAXParserFactory, DocumentBuilderFactory, and TransformerFactory. For each of these factories, you can choose from the following options:
Platform Default The default parsers are used and the entities custom class list is configured to load them. EAServer Manager adds the following JAR files to the entity’s custom Java class list (displayed on the Java Classes tab in the Properties dialog for the entity):
crimson.jar (for SAXParserFactory or DocumentBuilderFactory)
xalan.jar (for TransformerFactory)
Not Configured When this setting is in effect, the parsers configured in the server’s CLASSPATH and BOOTCLASSPATH setting are used. The parser classes are the same as for the Platform Default setting, but the classes are loaded by the Java system class loader.
You must use the Not Configured option to prevent overriding JAXP settings in child entities. For example, to use the Custom option in a component, the server, application, and package that contain the component must use the Not Configured option. If all entities in the hierarchy use the Not Configured option, JAXP classes are loaded by the system class loader.
Custom Allows you to specify a class name in the JAR file containing the specified class. The JAR file must be in the WEB-INF/lib directory for Web applications, or in the EAServer java/classes directory for all other entity types.
EAServer Manager sets the entity’s Factory property to the class name, and adds jaxp.jar and the JAR file you specified to the entity’s custom class list.
Precedence of JAXP properties The parser configuration at the highest level has precedence. For example, if you configure a parser at the server level, the server setting specifies the parser used in all components and Web applications running on that server. To prevent overriding the settings of child entities, specify the Not Configured setting in parent entities.
|Copyright © 2005. Sybase Inc. All rights reserved.|